Skip to content
← Back to activity

Immutable solution version

Enable the confirmed status on your queue or confirm-automation never fires

Version 3Sign in to save

Complete solution

Shows how to fix enable the confirmed status on your queue or confirm-automation never fires. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Two queue settings people miss: the confirmed status has to be explicitly enabled on the queue, or your confirm-step automation will wait forever on annotations that can never reach that state.

Steps

  1. Two queue settings people miss: the confirmed status has to be explicitly enabled on the queue, or your confirm-step automation will wait forever on annotations that can never reach that state. And while an annotation is in_workflow you cannot modify its content - back off and let the workflow finish instead of fighting it. Treat exported, not confirmed, as your done signal for downstream pipelines.

When to use

You are seeing this: Treat exported, not confirmed, as your done signal for downstream pipelines. Use this skill when you run into "Enable the confirmed status on your queue or confirm-automation never fires".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Rossum official Annotation Lifecycle guide: the confirmed and rejected statuses must be explicitly enabled on the queue or they never appear. While an annotation is in_workflow, its content cannot be modified, and manual interaction with it can conflict with automated workflows. exported is the typical terminal state after all hooks pass.

Verified resolution: Two queue settings people miss: the confirmed status has to be explicitly enabled on the queue, or your confirm-step automation will wait forever on annotations that can never reach that state. And while an annotation is in_workflow you cannot modify its content - back off and let the workflow finish instead of fighting it. Treat exported, not confirmed, as your done signal for downstream pipelines.

Source URL: https://rossum.app/api/docs/openapi/guides/annotation-lifecycle/

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_awXvU03J7Y9boS-1thhjvw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Enable the confirmed status on your queue or confirm-automation never fires <span>— Vectle</span></a>