Manual Runs

How Lead360 helps

Manual Runs let an authorized user start an automation for a controlled target and input set, then inspect the resulting execution. This is useful for one-time operations and testing, while preserving the same validation, approval, logging, and tenant boundaries as other automation runs.

When to use this area

Use a Manual Run when the workflow should begin now and a person can verify the exact automation, target records, inputs, and expected effects.

Before you begin

• Open the current published automation version and review every step.
• Select a small, controlled target set.
• Confirm external sends, financial actions, deletions, and customer record writes have the required approval.

What creates a Manual Run

1. A Manual Run starts when a team member selects contacts and manually enrolls them into a campaign or eligible automation. It is different from an Automation Run created by a trigger.
2. One row groups the original enrollment request and shows the campaign, workflow steps, channel or type, contact count, execution count, status, and start and completion times.

Review the enrolled work

1. Search by campaign name or filter by run type, then open Contacts to verify exactly which people were included and whether each execution succeeded, paused, or failed.
2. Workflow updated means the current published workflow may differ from the version used by that run. Review the current steps before repeating it.
3. A Completed batch can still contain an individual failed execution, so inspect the contact results before treating the whole audience as successful.

Use Re-run all carefully

1. Re-run all creates new executions for the original enrolled contacts; it does not continue the old executions in place.
2. Before rerunning, correct the failure and confirm earlier steps did not already send messages, add tags, create opportunities, notify staff, charge money, or change an external system.
3. The button is unavailable when the workflow is disabled, unpublished, no longer enrollable, still running, or lacks recorded contacts.

Use Ask360 here

Ask360 can summarize recent Manual Runs, filter them by campaign or status, explain contact and execution counts, surface recorded errors or workflow-version changes, and assess Re-run all eligibility. It never starts a rerun from this help flow.

Confirm the result

A completed Manual 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.

• Record the run identifier before leaving the page.
• Review each step status and output in Automation Runs.
• Confirm intended live changes in the owning product page and investigate partial failures.

Troubleshooting

The run is blocked before starting

Resolve missing inputs, permissions, connector mappings, disabled resources, or approval requirements shown by validation.

The run completed with an unexpected result

Inspect the exact version and inputs captured by the run, then compare each step output with the live target record.