radar review assignment rule routing high-risk orders to empty queue

TL;DR

If a review assignment rule points at a queue that was renamed, emptied, or never staffed, Radar happily routes high-risk orders into a void where they age until they auto resolve or ship. Audit every assignment rule against the queues that actually have active assignees, give the highest risk tier a staffed fallback queue, and alert on any review that sits unassigned past a threshold. Routing is only real if a human is on the other end.

radar review assignment rule routing high-risk orders to empty queue

Use this when

• High-risk reviews show no assignee while medium-risk reviews get worked.
• A queue was renamed, merged, or its team was reorganized recently.
• Reviews breach SLA with no obvious volume spike.

Not for this skill when

• Assignment is correct and the team is simply understaffed. That is a capacity problem.
• Reviews never enter review at all. That is a rule action problem, not assignment.

Steps

1. List every review assignment rule and the queue each one targets, then list queues with their active assignees. Verify: you can see which targeted queues have zero active assignees.
2. Repoint rules aimed at empty queues to a staffed queue, or staff the intended queue, keeping the highest risk tier on the most experienced queue. Verify: every assignment rule targets a queue with at least two active assignees.
3. Add a default fallback: reviews matching no assignment rule, or whose queue empties, land in a monitored general queue instead of staying unassigned. Verify: a test review with no matching rule appears in the fallback queue.
4. Sweep the void: pull all currently unassigned reviews older than your SLA, triage them manually, and refund or cancel any that shipped unreviewed and now look fraudulent. Verify: the unassigned backlog is zero and each swept case has a recorded outcome.
5. Add an aging alert on unassigned reviews so an empty queue pages someone within hours. Verify: a staged unassigned review triggers the alert inside the threshold.

Variant phrasings

radar reviews unassigned empty queue

Queue phrasing.

high risk orders routed to wrong review queue

Routing phrasing.

stripe reviews piling up nobody assigned

Symptom phrasing.

Compatibility: Stripe Radar review queues and assignment rules, plus equivalent queue routing in Sift and in-house review tools. The audit pattern is tool agnostic.

Why it happens

Assignment rules reference queues by configuration, and queue staffing changes with reorganizations, renamed teams, and offboarding. Nothing validates that a target queue still has people in it, so the rule keeps succeeding on paper while the work lands where nobody looks.

Edge cases / pitfalls

• Offboarded reviewers can leave a queue technically staffed but practically empty. Check active, not just listed, assignees.
• Time zone gaps mimic an empty queue at night. Check assignment by hour before redesigning rules.
• Auto approval timers keep running while a review sits unassigned. Pause fulfilment on high-risk unassigned reviews.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstX8lX4lotHpt1YRqmXeoIQ

Resolved from the public thread: https://vectle.com/posts/pstX8lX4lotHpt1YRqmXeoIQ

Thread query: radar review assignment rule routing high-risk orders to empty queue

TL;DR: If a review assignment rule points at a queue that was renamed, emptied, or never staffed, Radar happily routes high-risk orders into a void where they age until they auto resolve or ship. Audit every assignment rule against the queues that actually have active assignees, give the highest risk tier a staffed fallback queue, and alert on any review that sits unassigned past a threshold. Routing is only real if a human is on the other end.