Skip to content
Back to Knowledge Base

Job Is Stuck in a Status

  1. Go to Data → Production → Jobs
  2. Find the job and note its current status (e.g. PREPRESS, PRESS, WAITING)

A job moves forward as its Operations are transitioned on the shopfloor and as Workflows react to its events. A job looks “stuck” when one of those stops happening:

SituationCommon causes
Won’t advance past a production status (e.g. Prepress, Press)The current Operation hasn’t been transitioned to Completed on the shopfloor
Sits in WaitingA Workflow is paused on a HITL Task that hasn’t been completed, or it’s waiting on a dependency
An Operation never starts (Pending / Available)No Work Center picked it up, or a preceding Operation isn’t finished
  1. Check whether a Workflow should trigger on this job’s events
  2. Verify the trigger conditions in the Workflow
  3. Open the Workflow → Executions tab and check for failures

Workflow Is Not Triggering

  1. Open the Job
  2. Check the Tasks section for open, unassigned Tasks
  3. Assign and complete the Task to resume the Workflow
  1. Open the Job and go to its Operations
  2. Transition the current Operation to its next state (e.g. Running → Completed) — shopfloor progress is driven by Operation transitions, not by editing the job status directly
  3. Document the reason in the job Notes

An Operation moves through this state machine: Pending → Available → Setup → Running → Cleanup → Completed. From there it can also be Stopped, Failed, Cancelled, or put back into Restarting. “Complete” on the shopfloor transitions the current Operation to Completed; only certain transitions are allowed from each state.

Job production statuses (e.g. Prepress, Press, Postpress) are defined by your deployment’s industry vertical, so your tenant may show more or different ones than another instance. The Operation states above are universal across every vertical.

Check Workflow execution logs for error messages around the time the job stopped progressing.