A run says "Never finished"
Never finished is a label, not an error message. Beezr writes a run down as started the moment it begins, and updates it when it ends. A run that is still marked as started more than 1 hour later is shown as Never finished. Younger runs show as Running.
You meet the label in three places: the Never finished filter and counter in the run debugger, the Never finished pill on the Designer home, and the first line of an affected run, Started, never finished.
Is the run really stuck, or waiting on purpose?
Section titled “Is the run really stuck, or waiting on purpose?”Check. Open the run and read the last step on the Steps tab. A Wait step holds the run while it waits. The step itself says that for waits longer than a few minutes you should schedule a separate workflow instead.
An Approval task pauses a workflow until someone decides. Open Tasks in App space and look for the task. If it is there, the run is waiting for a person.
Fix. For a long wait, split the work. Let the first workflow end, and start the next part with a scheduled workflow that loads what is due. For an approval, ask the approver to decide.
Did the server stop in the middle of the run?
Section titled “Did the server stop in the middle of the run?”The debugger explains it: the run was started and never closed, usually because the server restarted in the middle. A run like this lists no steps, because steps are logged as they finish.
Check. Look at the time. Several Never finished runs from the same minute point to a server restart.
Fix. Start the work again. For a record-triggered workflow, save the record again or press the button that starts it. For a webhook, send the call again. Before you do, check what the first attempt may already have done, such as an email sent or a record created, so you do not do it twice.
Is one workflow always ending this way?
Section titled “Is one workflow always ending this way?”Check. On the Designer home, a flow whose last run never finished appears under Needs attention with the text Its last run started ... and never finished. Open it and read several runs.
Fix. If every run hangs, look at the last step with a mark that says Didn’t finish in a failed run, or the last logged step in an old one. Steps that call outside systems are the usual suspects. A REST API step has retries and waits you can shorten. See REST API.
How do I focus on recent runs?
Section titled “How do I focus on recent runs?”The counters follow the period you choose. Pick Last 14 days on the Designer home, or a period in the run debugger, to look at recent runs. Use All time when you want the whole history.
What's next
Last checked