Runs
A run is one pass through a workflow. Lodol records every run step by step, emails you when one fails, and counts each run once however many steps it takes.
Each time a workflow starts, Lodol creates a run: one pass through the workflow from its trigger to its last step. In the Stripe example, every payment that comes in is one run.
Every run is recorded
A run's history shows every step it took, in order: what each step did, when, and how long it took. When a run fails, the history shows the step that stopped it. Open it from the workflow, or read it with the API.
If a run fails, you get an email as soon as it does, and a notice in Lodol. Your AI tool can read the same run, work out what went wrong and fix the workflow.
Run statuses
| Status | What it means |
|---|---|
queued | Started, and about to begin its first step |
running | Working through its steps |
success | Reached the end of the workflow |
failed | A step failed and the run stopped there |
stopped | Someone stopped it before it finished |
Stopping a run doesn't undo the steps it already completed: a message it sent stays sent. See Handle failures for keeping a run going when one step fails.
Deleting runs
A finished run can be deleted from its page, or several at once by ticking them in the Runs list. The runs it started go with it: the runs its trigger started, and the runs of the workflows it called. A run that is still going has to be stopped first.
Deleting a run can't be undone, and needs the Delete runs permission in your role. It doesn't give back the run it counted as. Lodol also deletes finished runs on its own once they're older than your plan keeps them.
Some steps wait
Request approval pauses a run until a person answers. The run waits without using any resources, then carries on from that step with the answer. Wait pauses a run for a set time, or until a date and time.
What counts as a run
Your plan includes a number of runs each month. A run counts once, however many steps it takes, whether you started it or a trigger, a schedule or the API did. These don't count:
- a workflow that is turned on and waiting for its trigger
- a workflow that another workflow runs with a Run a workflow step
Runs reset on the 1st of each month (UTC). The workspace owner gets an email when 80% of the month's runs are used. If they run out, new runs pause until the 1st, unless you add more runs or turn on extra runs in Billing. See pricing for each plan's runs.
Next
Inputs and outputs
Inputs let one workflow run for many cases, such as a report for any client. Outputs are what it hands back to a workflow that runs it.
Connections and secrets
Workflows use your app accounts through connections, and your own API keys as secrets. Both are encrypted, used by name, and never shown in a workflow or to your AI.