HomeTroubleshooting Hub › Workflow stuck

Workflow stuck

Purpose: Unstick workflow instances and drain backlogs without losing in-flight approvals.

Who this page is for

AudienceWhy it matters to you
Backend engineersCustom step owners
Platform engineersBacklog management

Which kind of stuck?

ObservationLane
One instance sits at a stepSingle-instance lane
Thousands RUNNING, growingBacklog lane
Nothing processes at allEngine lane

Single instance

Workflow console → instance → open its history: which step, since when?

Step typeUsual cause
Participant stepIt's waiting for a human — the Inbox item is assigned to a group nobody checks, or the assignee left (reassign; then fix group-based assignment governance)
Process step (custom)Exception — error.log at that timestamp; fix cause, then retry the step from console (idempotency earning its keep)
GOTO/split logicModel logic dead-ends — model bug, terminate + fix model

Backlog lane

Engine lane

No workflow progresses: job queue topology stuck (restart the queue bundle/instance in a window), a launcher storm (mis-scoped launcher triggering on everything — check launcher configs against recent changes), or repository-level sickness (memory & CPU).

Draining etiquette

Terminating instances loses approvals in flight — inventory by model + business meaning before mass actions; retry in chunks; tell content ops what was terminated so submissions re-enter (session 9 flows).

Quick navigation