LoopfourA workflow did not run
Work out why a workflow did not run when you expected it to, by checking whether it is deployed, how it is started and its connections.
You expected a workflow to start, on its schedule, from an email or from a change in a connected system, and nothing seems to have happened. Work through the causes below in order.
It ran, but failed or is waiting
Most likely cause. The workflow did start, but the run failed before its first step, or it is waiting for an approval.
Fix. Open Runs and look at the Needs attention tab. A run that could not start says so, for example "Didn't start: QuickBooks isn't connected to this workflow". Follow the fix shown on the run. See Fix and retry a failed run.
The workflow is not live
Most likely cause. A workflow starts on its own only when its status is Active. A workflow that is Draft, Paused or Archived does not start from its schedule, an email, a connected system or the API.
Fix.
Check the status
Open Workflows. The status shows on each workflow, and you can filter the list by Draft, Active, Paused or Archived. The same status shows at the top of the editor.
Make it live
Open the workflow and select Deploy, then Deploy again to confirm. Studio says the workflow is now active. An archived workflow must be unarchived before it can be deployed.
Scheduled times that pass while a workflow is not active are skipped. They are not run later when you deploy. If you missed a run, start it yourself with Run a workflow on Runs.
The schedule is not what you think
Most likely cause. The schedule runs in the time zone set on the workflow's schedule step, which may not be yours.
Fix. Open the workflow, select the schedule step, and check Schedule and Timezone. Deploy again after a change. See Run a workflow on a schedule.
The email did not start it
Most likely causes.
- The email went to a different address. Each workflow that starts from email has its own address, shown on its email step as Inbound Address.
- The email did not pass the step's Filters. Loopfour ignores an email whose sender is not on the allowed senders, whose subject does not match the subject filter, or that fails the sender authentication check.
Fix. Check the address the sender used, and check the Filters on the email step. See Start a workflow when an email arrives.
The connected system did not start it
Most likely causes.
- The connection to that system has expired or been disconnected. See A connection stopped working.
- The workflow listens for a different event than the one that happened, for example a deal created rather than a deal won.
Fix. Check the connection under Integrations, then check the event chosen on the workflow's first step. See Start a workflow when something changes in a connected system.
Still stuck
Send support the workflow name, when you expected it to run (with your time zone), and how it should have started. See Get help.
Help and troubleshooting
Find the fix for a problem by its symptom, such as a workflow that did not run, a connection that stopped working or a missing approval.
A connection stopped working
Fix a connection that stopped working: reconnect the system, check the permissions of the account you used, and replace access that expired.