Runs

Open the «Runs» tab of a workflow. The right panel, «Run history», lists the runs, newest first, each with its state, "Run #n", its credits and how long ago it was queued. Click one to see it.

• The canvas draws the version that ran, not the draft, so an old run is shown as it really ran even if the workflow has changed since. A card is coloured by its step state: «Not reached», running, waiting, completed, failed or «Caught error» (muted red and dashed: a step that failed inside a Try, which caught it and let the run go on). A card shows its credits when it used any.
• A card at the top right shows the state, when the run resumes (if waiting), its duration, when it was triggered and when it ended, «Steps run» and «Credits». When it has failed, it shows the error message in red.
• Click a step to see what went into it («Input») and what came out («Output»), or, for a step that failed, «Error». The viewer refreshes by itself every few seconds while the run is queued, running or waiting.
• The counters at the top of the editor's side panel («Completed», «Failed», «In progress», «Average time») count all the runs of the workflow that still exist.

• There is no filter, search or pagination: it shows the 100 newest runs. "Run #n" is the position in that list, so the numbers shift once there are more than 100 runs and older runs cannot be reached.
• When a step ran several times (in a loop, or after a jump), the step panel shows the first execution's input and output. The card's colour and credits cover all of them.
• «Triggered» is the moment a worker first picked the run up, not when it was queued.
• The version number of a run is not shown.
• Attempts are not shown. A run that is retrying is just waiting, and the reason for the retry is not displayed at run level.

• Only administrators can use these buttons. The interface does not show an error if you press one and cannot (a non-administrator gets nothing, and a run that changed state meanwhile just does not move).
• A paused run is never woken by the platform, even after you add credit or turn on «Turn on pay-as-you-go». Press Resume.
• Retrying cannot fix an error that comes from the workflow itself, such as an invalid definition, a loop limit or more than 500 items: it fails the same way. Fix the workflow, then run again; a retry keeps using the old version.
• Only a failed run can be retried. A cancelled run cannot, and neither can a failed run once it has been deleted after 90 days.

Every run is created by a trigger, by Retry or by Resume (which reuse the run). What decides whether two requests make one run or two:

Filmo does not serialize the runs of one workflow: two runs of the same workflow can run in parallel.

A completed, failed or cancelled run is deleted 90 days after it ended, together with its steps, inputs, outputs and errors. Runs that are queued, running, waiting or paused are never deleted. Deleting a workflow deletes its runs at once. Run data can contain your customers' data, so this is also the time it stays in the run history.

Any member can see a workflow's runs unless the workflow is private; then only its creator and administrators can. Failure notices go to the creator or the administrators; see Errors and retries.