Binary Artifacts

Runs can produce downloadable files - captured configs, generated reports, collected archives. Artifacts → Binary Artifacts in the sidebar is the storage-management view over all of them: every downloadable binary artifact across every run, with the total storage usage shown in the header. (The page lived under Settings before; the old address redirects.)

Use it when stored artifacts accumulate and you want the space back, or when you need to collect outputs from many runs at once.

What you can do

• Download a single artifact from its row menu, or select several and use Download selected to get them as one ZIP file.
• Delete content to purge an artifact's stored bytes - singly or in bulk. This frees storage but keeps the record: the run's Artifacts tab still lists the artifact, marked as deleted, so the run's history stays complete. Deletion cannot be undone.

Each row links to the run that produced the artifact, so you can check the context before deleting. The Status column tells you whether the content is still available or already purged.

Where artifacts come from

Artifacts are created by steps while a run executes; you view them in context on the run's detail page under the Artifacts tab - see running flows. This page is only the cross-run management view; nothing is uploaded here.

Managing binary artifacts is a platform admin's job: the page spans every organization's runs, so it is shown to platform admins only.