## TL;DR
Fix this in community moderation queue by acting on the exact problem first: fix triage by adding queue filters for legal, safety and personal data reports, routing those types to an on-call owner with an alert on arrival, and sweeping the existing backlog once with those filters so every buried urgent report is found, not only the one that was reported. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

```text
Urgent legal complaint buried under spam reports in the queue
```

## Use this when
- The operation in community moderation queue fails with this exact message or symptom: Urgent legal complaint buried under spam reports in the queue.
- The same failure repeats on retry with unchanged inputs.
- Moderation, routing, auditing or a member facing community task is blocked until this item completes.

## Not for this skill when
- The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
- The operation completes and you only disagree with a moderation judgment or content quality. That is a policy review, not this failure.

## Steps
1. Reproduce the failure with the smallest scope that still shows it in community moderation queue, and copy the full message plus the post, thread, report or member involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: fix triage by adding queue filters for legal, safety and personal data reports, routing those types to an on-call owner with an alert on arrival, and sweeping the existing backlog once with those filters so every buried urgent report is found, not only the one that was reported. Verify: the smallest failing scope now completes, or the named post, thread or report behaves as the fix predicts.
3. Check the neighbouring posts, threads, reports or members that share the same setting, rule or workflow, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in community moderation queue on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts or status against the source in community moderation queue so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

## Why it happens
Buried urgent reports are a classification failure at intake, and one rescue without intake filters guarantees the next legal complaint is buried the same way.

## Variant phrasings

### Urgent legal complaint buried under spam reports in the queue
The verbatim form searchers paste from the console, queue or report. Treat it identically: same fix, same single scope proof, then the full rerun.

### How to fix - how to fix moderation queue triage error urgent legal complaint buried under spam reports fails error
The how to phrasing for the same failure in community moderation queue. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

### community moderation queue troubleshooting for this failure
The symptom first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

## Edge cases
- If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
- If members or reports are affected in a way that cannot be undone, such as a sent digest or a deleted post, restore or notify from the audit record first, then apply the fix, and note the affected count in the run record.
- If two settings or rules could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: community moderation queue at current versions, plus the admin console, moderation queue or API the query names; no extra tooling beyond the source system access needed to verify counts.

## Provenance

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