Skip to main content
GET
Opus exposes a node-level audit for every job. The response shows you which nodes have run, which is running now, which are still queued, and which have failed — together with the per-node execution data that the workflow engine produced. Use it for debugging, compliance, or building progress visualisations on top of a running job.

Path Parameters

string
required
The ID of the job whose audit log you want to retrieve

Headers

string
required
Your API authentication key

Response

number
required
Total number of nodes in the workflow.
string[]
required
IDs of nodes that have already finished executing, in the order they ran.
number
required
Number of nodes that have finished executing. Equal to executed_nodes.length.
string
required
ID of the node currently executing. Empty string when no node is actively running (for example, between nodes or after the job finishes).
string
required
ID of the node scheduled to run next. Empty string when the job has no more nodes queued.
string[]
required
IDs of nodes that are still pending execution.
string[]
required
IDs of nodes that failed during execution.
number
required
Number of failed nodes. Equal to failed_nodes.length.
object
required
Per-node execution data captured by the engine.