Workflows and automations

New rules start as drafts. Activate the rule after reviewing its trigger, conditions and actions.

Check that the event occurs afterwards and in the same company. If there is no run, review plan limits too. If a run exists, open its details to find blocked, skipped or failed steps.

Use the test environment and inspect the run details. Steps with external effects are neutralised in tests.

A completed test run does not prove that a real email was delivered. Review recipients, permissions and integrations before using the rule in the live environment.

No. Each run retains the rule version and event data with which it started. Editing creates a new version for subsequent runs.

When investigating an outcome, check that run’s version. Comparing it only with the current editor may lead you to conditions that did not exist at the time.

Open the history and identify the step and reason. Review permissions, recipients, configuration and integration availability before retrying.

Some failures are retried after a delay. Parked runs may allow replay and repeated failures can disable a rule. Use the action available for that case and check whether any steps already completed.