Versions and storage

SCMotif keeps the earlier files of each data source and the earlier versions of workflow results, and records the inputs each run used. Those files and results count against your account's storage limit. You can inspect or restore an earlier file or version, and review old ones to free space when you no longer need them.

What gets a version

• A data source holds every file added to it, numbered in the order they arrived. The newest is its latest file. An upload adds a file; so does each successful save of a Save Data step, into the data source that step writes.
• A Create Scenario step publishes a new version of its scenario when it successfully saves. Scenarios shows the current version and offers its history.
• Restore as current saves a new current version of a scenario from an earlier one, and Restore as latest copies an earlier file as a data source's newest. Neither changes the others or reruns a workflow.

Each producing step owns its history. A different step, or a copy of a workflow, creates a separate data source or scenario, even if you give it the same name.

Bringing in a corrected or refreshed upload

A file's name is never given to another file, so an upload under a name already used in the project is refused. Give the new file a name of its own, such as lanes-corrected.csv or shipments-2026-11.csv, and choose Add file on the data source it belongs to. It becomes the latest file, and workflows reading the latest file use it from their next run. Existing runs keep their record of the file they read.

Which inputs a run reads

When a run is accepted, Import Data resolves its data source to the latest file, or to the one file chosen in its File setting, and Load Scenario resolves the selected scenario to its current version. The run records those exact inputs and keeps them fixed while it waits in the queue and runs. A later save or restore affects future runs, not one already accepted.

Load Scenario reads a saved result; it does not rerun the workflow that produced it. See Import Data and Load Scenario for their settings.

Find what an earlier run used

1. Open Workflows → Runs and select the run by its workflow and date.
2. Choose View snapshot to see the workflow as it was for that run.
3. Expand Run provenance. Source inputs records the input identities and content hashes; the same panel records the product build and packages that ran the workflow.
4. For a scenario the run saved, open its History on Scenarios. Inputs used lists the source files and scenario versions behind that result. An input that has been deleted is marked as deleted.

The record explains an earlier run even after its workflow changes. It does not keep a separate downloadable copy of every input: deleting a source removes its bytes while the run retains its identity and content hash. Run again uses the workflow and current inputs as they are now. See a run's page.

Open or restore an earlier version

For a data source, open Data Sources and press its N files link. Download saves the selected file to your computer; Restore as latest copies it as the data source's newest file.

For a scenario, open Scenarios → History. Open version shows the saved result in the Viewer. Restore as current makes a new current version from that result. See scenario history.

Future runs that read the data source's latest file, or the scenario, use what was restored. Existing run records and saved results stay as they were. Dashboards keep the scenario versions they already show until you explicitly update their results.

What counts against storage

Open Settings → Storage to see your account's limit and usage across all projects. The breakdown shows:

• Uploaded files: every file of every data source, uploaded or saved by Save Data, earlier files included.
• Scenario results: stored scenario tables, including earlier versions.

An unfinished upload reserves space until it finishes, is cancelled or expires, so that space is not available to other writes. Complete it or choose Cancel upload under Unfinished uploads if you no longer need it.

When the limit is reached

An upload that will not fit is refused. A full account refuses new workflow runs, and a run can also be refused before saving its results if there is no room then. Existing data is not deleted to make room. A result already past the storage check may finish saving and leave the account over its limit; further writes are refused until space is available.

Use Free up space from the refusal, a storage notice or Settings → Storage. After recovering space, retry the upload or run yourself; cleanup does not restart it.

Free up space

The review lists scenarios and data sources by project, with the previous versions or earlier files available for deletion and how much space they occupy. Selecting an item selects all its eligible previous versions, not a single version from its history.

Current versions and latest files stay. Earlier ones also stay when they are used by an unfinished run, chosen by name in an active workflow, required by a retained scenario result, or shown by a dashboard. Expand Why versions are protected to see what still uses them.

1. Select the scenarios or files whose eligible history you no longer need.
2. Press Delete previous versions… and review the names, number of versions and space to recover.
3. Press Permanently delete versions to confirm. Deleted versions cannot be opened, downloaded or restored.

The confirmation reports the space recovered from your allowance; stored files are removed in the background. If versions or their usage changed during review, follow the message and review the refreshed selection. If part of a mixed scenario-and-file selection was already deleted, the message says what was removed and what remains.

When no eligible history remains, you can remove data sources or entire scenarios you no longer need. Deleting a whole item also removes its history. Download anything you need to keep before deleting it.