Job History

Every time a workflow runs — automatically, manually, or via API — a job record is created. Find it in the Job History tab of any workflow.

The job list shows:

Run time — when the workflow started
Status — Completed, Failed, or Running
Duration — how long the run took
Trigger — what started it (schedule, event, manual, API)

Click any job to open the full run detail.

Inspecting a run

The run detail view shows every step that executed, in order.

Step status

Completed — the step ran successfully
Failed — the step threw an error
Skipped — the step was bypassed, for example a Condition gate blocked the path

Step input

The exact data passed into the step, including resolved template values at the moment of execution. This is invaluable for debugging because it shows what {{ $anythink.trigger.data.field }} actually resolved to at runtime.

Step output

The data the step returned. For Read Data steps this is the records fetched. For Run Script this is what your script returned. For Call an API this is the raw response body.

Error details

If a step failed, the error message is shown here.

Understanding "Condition evaluation failed"

When a Condition step's conditions are not met, the job is marked as Failed with the message "Condition evaluation failed". This is normal and expected when you are using a Condition step as a gate.

For example, if a workflow only processes blog posts and a different record triggers it, the Condition gate blocks it. The job shows as failed. This is the intended behaviour, not a bug.

Testing a workflow

You do not need to wait for a real event. Every workflow has a Test button in the canvas toolbar.

Testing a Timed or Manual workflow

Click Test and the workflow runs immediately. Any {{ $anythink.trigger.data.field }} references resolve to empty or null, so make sure your scripts handle missing data gracefully.

Testing an Event workflow

Click Test and provide a sample record as a JSON payload. This simulates what the trigger data would look like for a real event:

json

{
  "id": 42,
  "email": "alice@example.com",
  "status": "approved"
}

Testing an API endpoint workflow

Either click Test and provide a JSON body, or send a real HTTP POST to your endpoint URL. The job appears in history just like any other run.

Re-running a job

From the job detail view, click Re-run to execute the workflow again with the same trigger data as the original run. Useful for:

Retrying after a step was misconfigured and has now been fixed
Retrying after an external API was temporarily unavailable
Processing a record that was accidentally skipped

Common debugging tips

My Run Script step failed.
Open the job detail and click the step. The error section shows the JavaScript error. Common causes are accessing a property on undefined (check the previous step returned data), syntax errors, or unsupported JS syntax such as optional chaining.

My Call an API step returns an unexpected response.
Check the step output for the raw response and HTTP status code. Common issues include a wrong URL, missing auth headers, or an incorrect body format. Remember the URL field does not support template syntax.

My workflow runs but nothing gets created.
Look for a Condition step marked as Skipped. Check whether a Read Data step returned zero records. If you are running an ingest workflow, consider the dual-gate pattern to handle empty results safely.

The step input shows the wrong value.
The issue may be upstream in an earlier step or in how a template was written. Check the output of the step before it to trace where the value changed.

Monitoring and Testing