Storage¶
Storage is where SchemAlign surfaces physical outputs and operational files produced by integrations.
This area helps users understand what a run created, where artifacts were stored, and which logs or files may be needed for troubleshooting.
What Storage is for¶
Storage may include:
- generated files
- run artifacts
- exported datasets
- intermediate outputs
- node execution logs
- pipeline run logs
- files staged for downstream systems
How Storage relates to artifacts¶
An artifact is a physical or runtime output from a pipeline run. Storage is where users can inspect or manage those outputs when their access allows it.
Examples:
| Artifact type | Example |
|---|---|
| CSV output | graduates_202640.csv |
| JSON response | API response captured during a run |
| Log file | Node or worker execution log |
| Transformed result | SQL transform output written for a destination |
Operational guidance¶
Use Storage when you need to:
- confirm that a file was generated
- download or inspect a run output
- review logs for a failed node
- verify that an output name or path resolved correctly
- trace an integration issue from Overview into concrete run artifacts
Storage is not a substitute for secrets management
Do not store passwords, tokens, private keys, or other secrets as files in general storage. Credentials belong in Accounts or approved secret storage patterns.