Run history is not kept for ever. Each workflow keeps a set number of its most recent runs, depending on the company's plan, and older ones are removed as new ones finish. Files a run kept are removed with it. This article says exactly what is kept and for how long, so you can download anything you need first.
Who can do this
This applies to every workspace. The number of runs kept follows the company's plan, which the company's Owner can change.
Steps
- To see what is kept now, select Runs in the bar at the top of the page and choose Everything kept in the period menu.
- To keep a record of a run beyond that, open it and select Download the run log. See Export run history, or download a run log.
- To keep a file a run brought in, open the step that brought it in and select Download. See Download a file a run kept.
- To keep a list of many runs, select Export CSV on run history.
What happens next
Each time a live run of a workflow finishes, Bizomate keeps that workflow's most recent finished runs and removes the rest, with their steps and files:
| Plan | Live runs kept per workflow |
|---|---|
| Free | 10 |
| Starter | 20 |
| Pro | 200 |
| Enterprise | All of them |
Test runs are kept separately, per workflow:
- The last 20 test runs are kept whole for 7 days.
- A test run older than the last 20 loses its steps at once, and the run itself goes after 2 days. It stays that long because today's test runs are counted from it.
- Any test run older than 7 days is removed.
Good to know
- Runs are kept per workflow, not per workspace. A workflow that runs every five minutes does not push out the history of one that runs once a week.
- Runs that have not finished are never removed — a queued, running or waiting run stays until it ends.
- Files go with their run. A file is kept longer only while something that stays still uses it: another run that is kept, or data pinned to a step in one of the workflow's versions.
- Deleting a workflow deletes all of its runs and their files at once.
- Moving to a smaller plan removes the extra runs of a workflow the next time it runs; moving to a bigger plan keeps more from then on, but does not bring back runs already removed.
- Removed runs cannot be brought back.
- A removed run's page says That run is not here.
- The record of what a list step did is part of the run, and goes with it. The rows in the list are not affected.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| That run is not here — History keeps the most recent runs of each workflow; older ones go. It may also belong to another workspace. | Newer runs of the workflow replaced it, or it belongs to another workspace. | Switch to the right workspace. A removed run cannot be brought back. |
| Download on a file says it cannot be found | The file went with its run. | Get the file from where it came from. |
| An old test run has no steps | It is older than the workflow's last 20 test runs, so its steps were removed. | Run the test again. |