LoopfourRuns: see what happened
Use the Runs list to see each time a workflow ran, what its status means in plain words, and which runs need your attention right now.
Each time a workflow starts, Loopfour records a run. The run keeps what each step received and produced, any approval decision, and where it stopped if something failed. The Runs page is where you check that work happened, find what needs you, and pull support for a review.
- TriggerThe workflow startsOn its schedule, from an email, from a change in a connected system, or when you select Run.
- StepSteps run in orderEach step's input and result is recorded.
- ApprovalIt may wait for youThe run shows Waiting for approval.
- OutputIt endsCompleted, Failed or Stopped, with the record kept.
How it works
- A workflow starts a run when its trigger fires or you select Run on an Active workflow.
- Steps record their results as they finish.
- You review the status and open a step to inspect its result.
Open the Runs page
Select Runs in the sidebar. To see the runs of one workflow only, open the workflow and select Runs at the top of the editor.
The tabs
| Tab | What it lists |
|---|---|
| All runs | All runs, newest first. It opens on the last 7 days. |
| Needs attention | Runs that failed, including runs that could not start, and runs waiting for an approval. Stopped and paused runs are not listed here, because a person chose to stop or pause them. |
| Approvals | Only the runs waiting for a decision. This is the same view as Approvals in the sidebar. |
| Running | Runs that have not ended: queued, running, paused and waiting for approval. |
| Audit trail | The company-wide record of who did what and when. See Audit trail. |
Needs attention, Approvals and Running show runs of any age, so an old failure or an old request is not hidden.
What each status means
| Status | In plain words |
|---|---|
| Queued | The run is about to start. No step has run yet. |
| Running | Steps are being carried out now. |
| Waiting for approval | The run is paused at an approval step until someone decides. |
| Pausing | Someone asked to pause. The run pauses once the step that is running now finishes. |
| Paused | A person paused the run. It does nothing until someone resumes or stops it. |
| Completed | All steps that were meant to run finished. |
| Failed | A step failed, the run could not start, or an approval was rejected or timed out. The run shows the reason. |
| Stopped | A person stopped the run before it finished. |
Narrow the list
Above the list you can:
- Search by run ID.
- Filter by Workflow, Status, Trigger (App event, Schedule, API, Manual, Subworkflow or Event) and date range (Last 24 hours, Last 7 days, Last 30 days or All time).
The list shows 10 runs at a time. Select Load more to see more, up to 100. To find an older run, narrow the filters.
Act on a run from the list
Each row offers the one action that fits its state:
- Approve and Reject on a run waiting for approval.
- Retry on a failed or stopped run. See Fix and retry a failed run.
- A connect button on a run that could not start because a system is not connected. It takes you to Integrations.
- Pause, resume or stop on a run that is still going, depending on its state. Stopping asks you to confirm and tells you what will be interrupted.
To read a run step by step, select its name. See Read a run step by step.
What Loopfour does and does not do
A run record shows what the workflow attempted and what its steps returned. It does not prove an accounting entry is correct. Compare important results with the source document and ledger. Retrying can repeat writes, so review the retry plan first.
Next
Approve or reject a request
Decide on an approval request from Approvals in Studio, from the email you received or from Slack, and see what the workflow does next.
Read a run step by step
Open a run and read it one step at a time: what each step received, what it produced, and where the run stopped if something failed.