Run History & Debugging

Run History & Debugging

Run Statuses

Each time an automation is triggered, a “run” is created. Runs have the following statuses:

• Running — The automation is currently executing its steps.
• Waiting — The automation is paused at a delay node and will resume automatically when the wait time elapses.
• Completed — The automation finished all steps successfully.
• Failed — The automation encountered an error and stopped. The failing node and error message are recorded.
• Cancelled — The run was manually cancelled by a user.

Run History

Go to the Runs tab on any automation to see every execution. Each run shows:

• The trigger event that started it.
• The current status.
• When it started and when it completed (or failed).
• The document, contact, or form submission that triggered it.

Step-by-Step Logs

Click on any run to see the detailed execution log. Each step shows:

• Which node was executed.
• The action or condition type.
• The step status: Started, Completed, Failed, or Skipped.
• Input data passed to the node.
• Output data produced by the node.
• Execution duration (in milliseconds).
• Error message (if the step failed).

Debugging Failed Runs

When a run fails, the log shows exactly which node caused the failure and the error message. Common issues include:

• Missing or invalid email address in a Send Email action.
• Invalid field mapping in a Create Contact or Update Contact action.
• Unreachable webhook URL or timeout in a Webhook action.
• Document is in a locked status and cannot be updated.
• Maximum step limit (100) reached — possible infinite loop in the workflow design.

Cancelling Runs

If a run is stuck in “waiting” or “running” status, you can cancel it manually. This stops execution immediately — no further actions will run.

Duplicating Automations

Duplicate an existing automation to create a copy with all nodes and connections. The copy starts in Inactive state. This is useful for creating variations or A/B testing different workflows.

Context Data

When a trigger fires, the automation run receives context data that is passed to every node. The available context depends on the trigger type:

• Document triggers — Document ID, type, status, recipient name/email, owner name/email.
• Form triggers — Form ID, form name, submission ID, created contact (if applicable).
• Contact triggers — Contact ID, name, email, and all field values.
• Record triggers — Record ID, entity type, and all custom field values.
• Payment triggers — Payment amount, method, document details.
• Booking triggers — Booking ID, guest name/email, scheduler name, start/end times, location, status, custom field values.

Actions and conditions can reference this context data to make dynamic decisions and populate fields.