Jobs & Execution

A job is a running instance of a workflow version. When you submit a job, the engine executes each step in sequence, tracking state transitions and execution history.

Job Lifecycle

SubmitJob ─→ PENDING ─→ RUNNING ─→ SUCCEEDED
                            │
                            ├──→ FAILED (step error)
                            └──→ CANCELLED (manual cancel)

Status	Description
PENDING	Queued, waiting for the scheduler to pick it up
RUNNING	Engine is actively executing steps
SUCCEEDED	All steps completed successfully
FAILED	A step encountered an error; resumable via ResumeJob
CANCELLED	Manually cancelled; resumable via ResumeJob

Monitoring Jobs

• GetJob — primary polling endpoint for status, timestamps, and parent/child hierarchy
• ListJobs — paginated list with filtering by status, workflow name, date range
• GetWorkflowState — deep inspection of step-level execution history and data

Execution History

Each step execution is recorded with:

• Input data passed to the step
• Output payload returned by the step executor
• Execution status (success, failure, successful_but_incomplete)
• Start and end timestamps
• Any errors or warnings

Resuming Failed Jobs

When a job fails, you can resume it from the last completed step rather than restarting:

curl -X POST https://api.justworkflowit.com/organizations/$ORG_ID/jobs/$JOB_ID/resume \
  -H "Authorization: Bearer $TOKEN"

The engine picks up where it left off, preserving all prior step outputs.