Runs and their history
How to start a run, read how it went step by step, and whose name the changes a run makes carry.
Each time an automation runs, Sterodata records the run and each of its steps, so you can see what happened without asking anyone.
Start a run
Save your changes first, then choose Run at the top of the editor. A message says how the run went, or that it has started when it is still going. If it failed, the message carries the reason.
An automation runs once at a time. Starting it while a run is still going is refused (a button on a table says it is already running), and a scheduled start that falls during a run is skipped.
Recent runs
The Recent runs panel, beside the steps, lists the latest 50 runs, newest first. Each reads what started it, when, and how it went, for example Manual run · 2m ago · succeeded, with how long it took. Refresh reads the list again.
| A run that… | Means |
|---|---|
| succeeded | Every step finished. |
| partly succeeded | A step failed and was set to Continue to next step; the others ran. |
| failed | A step failed and the run stopped there. |
| running, waiting to start | It has not finished yet. |
Select a run to see its steps in order, each with how long it took and its output. A failed step says what went wrong and, where it can, what to do next; View details shows the rest.
Whose name a run's changes carry
- A run you start, with Run or a table's button, acts as you: the rows it writes show you as having created or changed them.
- A scheduled run acts as the workspace's System user, because nobody pressed anything. Its rows show System.
Either way, the run can reach only what the automation itself was given when it was saved, never more than that because of who started it. See Automations.
Last updated 29 October 2026