Why did my process run fail or stop running?
Use this guide when a process has a Failed run, has stopped running, or seems stuck.
Errors appear on the process's Test tab, in the step details on the History tab (click a red step badge), and on the dashboard (hover over the ! pill). In the messages below, … stands for a name, address or value from your own set-up.
The process has stopped running
On the dashboard it shows Idle with no Next run. Usually:
- the last run Failed and Continue Schedule On Failure is off
- Schedule Period Minutes is empty or 0, so it only runs when scheduled
- someone cancelled the scheduled run
Fix any error, then click Requeue on the failed run or schedule a job on the Jobs tab.
Every record failed
The run error reads All N fetched record(s) failed. Open the run's records on the History tab and click a red step badge to see why. Usually it's one shared cause, such as a template or sign-in problem.
Schedule Expression errors
These stop the whole run:
| Message | What to do |
|---|---|
scheduleExpression '…' resolved to a time in the past (…). | A record's time had already passed. Filter the dataset so it only returns records whose time is still ahead, or change the offset. |
Invalid scheduleExpression '…'. Expected format: … | Correct the expression. It must be exactly {dynamic:DateTimeNow:N} or {recordData:Field:N}, with no spaces. |
Unknown dynamic key '…'. Only 'DateTimeNow' is supported. | Use DateTimeNow. |
recordData key '…' not found in record. | Add the field to the dataset's Select list, using that name in As. |
recordData['…'] value '…' cannot be parsed as a DateTime. | The field is empty or not a date for some record. Filter out those records. |
Other run errors
Dataset … not found.orContent … referenced as the process dataset is not a Dataset or REST Dataset.: pick a valid dataset on the process.Rule dataset … not found.: a rule condition points at a dataset that's been deleted. Fix the rule.- Data source and parameter errors: see the other troubleshooting guides.
A run is stuck on Running
Check the Jobs tab. If there are Process Record jobs waiting (for example, delayed by a Schedule Expression), the run will finish when they're done. If there's nothing waiting, a record job may have been cancelled or the run interrupted, and it won't finish on its own. Contact Three 17 support, and schedule a new run on the Jobs tab to restart the process.