Files
A File is durable storage owned by a Space. It can be uploaded by your application, produced by a Runtime, or exported from a Run. The File resource is the durable record; a Runtime workspace is only the live machine disk used while automation is running.
Three file surfaces
Files produced by a Runtime can be collected into durable storage and remain available after the Run ends. Files staged into a Runtime are copies for that Runtime workspace; staging does not move or delete the durable File.
Upload a File
The Space can be omitted to use the caller’s default Space:
file is a Blob. name, path, and metadata are optional. Use
spaceId when uploading to a Space other than the caller’s default:
Paths are relative to the Space’s storage namespace. Use a path prefix to
organize files; absolute paths and ./.. path segments are not allowed.
List and browse Files
list() returns one cursor page. iter() follows all pages automatically.
Available filters are:
To render a folder tree, request folder summaries:
With include: "folders", data contains files directly under the requested
prefix and folders contains immediate child-folder rollups.
Read, download, update, and delete
The File resource also includes downloadUrl when you want to download through
the returned URL instead of files.content().
File fields
Runtime workspace files
Use the built-in File Tools to transfer files through a live Runtime workspace:
See Stage Runtime file and
Collect Runtime file for the Tool
fields and path rules. Runtime workspace paths are relative to the workspace;
use path, not an absolute host path or the old runtimePath name.
Run files
List durable Files attached to one Run:
Use run.files.export when you want to
combine selected Run files into one durable archive File.

