For the complete documentation index, see llms.txt. This page is also available as Markdown.

Queue failures and recovery

Diagnose missing actions, stalled work, invalid states, and partial processing.

Queue recovery starts by identifying the layer that failed: permission, workflow stage, assignment, annotation validation, source processing, model inference, batch processing, or downstream release creation.

The operating model

Use this in production

  • A missing button usually starts with role, stage, selection, or resource-state checks.

  • Invalid annotations remain saved but require property or value correction before acceptance.

  • Rejected work needs a corrective route; failed processing needs operational recovery.

  • For partial batches, preserve succeeded items and retry only after remote-state inspection.

  • Escalate systemic failure patterns with affected IDs, counts, timestamps, versions, and redacted errors.


Related Unitlab capability guides: enterprise data annotation workflows