Automation Runs

How Lead360 helps

Automation Runs provides the evidence trail for each workflow execution, including the version used, target, inputs, step states, outputs, timing, and errors. Teams can distinguish a successful trigger from a successful business result and investigate failures without guessing.

When to use this area

Use Automation Runs after testing, publishing, or manually starting a workflow, and whenever a customer or staff member reports an unexpected automated result.

Before you begin

• Collect the approximate run time, automation name, and target record.
• Know the expected trigger and final effect.
• Avoid restarting the workflow until duplicate effects are understood.

What creates an Automation Run

1. An Automation Run starts when a published automation receives its configured trigger, such as contact activity, a form event, a schedule, or an approved system event.
2. Each row is one execution and shows the automation, trigger, resolved contact, status, start and completion times, and available investigation actions.

Investigate a run

1. Filter by status or search by automation, trigger, or contact. Open View to inspect every recorded step, duration, output, and sanitized error.
2. Failed identifies the step that stopped. Paused may require approval or external input. Succeeded means all recorded steps completed, but it does not prove the business outcome was correct.
3. Version changed means the automation was republished after this execution; compare the old and current steps before replaying.

Resume or replay safely

1. Resume from failure continues only when the runtime recorded a safe resume point. Restart creates a new execution from the beginning. Step replay repeats only the selected replayable step.
2. Confirm completed steps did not already send a message, create a record, update a contact, or call an external service. AI conversation messages require their own preview and approval.

Use Ask360 here

Ask360 can summarize and filter recent Automation Runs, inspect an automation by name, explain its failed step and recorded error, and report whether resume or restart is currently available. It never replays a run or sends a message from this help flow.

Confirm the result

A completed Automation Runs workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.

• Confirm the run used the intended automation version.
• Inspect every step, not only the overall status.
• Verify external sends and live record changes in their owning systems.

Troubleshooting

No run was created

Check whether the trigger event occurred, the automation was enabled, filters matched, and the target belonged to the correct sub-account.

A retry could duplicate work

Review idempotency and existing step outputs before retrying any send, payment, creation, or other non-reversible effect.