Weekly Challenge
SEASON 2 / CHALLENGE 06Participation closed

The Support Queue

A support desk needs a clear view of its queue. Fetch 24 personal tickets, count the open ones and find the urgent tickets within that queue.

Personal tickets
24
Required answers
2
Weekly rank points
15 / 12 / 12 / 11
01

How many tickets are open?

Count tickets whose status is OPEN. Return that total as b1.

02

How many open tickets are urgent?

Count tickets whose status is OPEN and priority is URGENT. Return that subset as b2.

Build, check, submit

  1. Import the starter and use the untimed eight-ticket practice while preparing.
  2. When participation opens, enter your existing account details and fetch your personal rows.
  3. Split tickets into items, add native filters and counts, then map the two Count outputs directly to Number fields b1 and b2.
  4. Optionally check the complete pair, then submit both totals, your sanitized workflow and your explanation.

Challenge rules

Build your own native workflow

Use HTTP Request, Split Out, supported native Filter or IF, Summarize Count and direct Number mappings to b1 and b2. Keep a connected calculation for both answers. Supported native Count export defaults are accepted.

No AI assistance

Do not use AI to interpret, plan, generate, debug, solve or explain this challenge. AI, Agent, MCP, Tool, Code and Function nodes are not allowed. Do not type fixed answers, compute them with arithmetic, use external ticket data or include pinned data.

Exactly two answers

Count all OPEN tickets, then count OPEN tickets whose priority is URGENT. Personal data contains 24 tickets. There is no third answer.

Timing and acceptance

Your first successful authenticated personal fetch starts the timer when participation is open. Practice stays untimed. Re-fetches retain the same tickets and first fetch. A correct supported final is accepted automatically. The first accepted evidence and finish are retained, with no pending replay or routine human approval during the season.

Checks and retries

An optional paired check returns overall correctness only. Four checks are allowed per rolling 15 minutes, up to ten paired attempts total. Submit and rules admissions allow 30 per rolling hour. A correct eligible final remains possible after ten wrong finals. Accepted retries return the original receipt without a new debit.

Export safely

Upload a JSON export no larger than 1 MiB. Blank Settings.key, remove credentials and pinned data, and keep your username and native calculation. Include your own explanation of 40 to 2,000 characters and at least eight words.

Rank and points

Least validated completion time leads. Exact competition ties share rank and points. Weekly points are 15, 12, 12 and 11. Existing Season 2 results remain separate and season totals include accepted weekly awards. Reward review takes place at season end.

Submit your C06 workflow.