Docs/Platform guides
Archiving, restoration, and history
Retire monitoring resources while understanding what stops, what is retained, and what can be restored.
Use lifecycle controls to retire resources deliberately. Archive, disable, and delete have different effects. Read the specific action’s impact and blockers before confirming it.
Find archived resources
Many resource lists offer Include archived. Archived resources are hidden from default active views and are generally read-only. Historical data can remain available through explicit archived-history views.
| Resource | Effect of archiving |
|---|---|
| Instrument | Stops ingestion and calculation; retains variables, constants, and historical values. |
| Ingested variable | Rejects incoming data using its ingestion name; retains history and the reserved identity. |
| Calculated variable | Stops new calculation; retains its current historical results. |
| Calibration constant | Retains its ID and value; active dependencies must be resolved first. |
| Dashboard | Makes it read-only; retains saved widgets and access grants. |
| FTP pipeline | Stops future polling; work already started may finish. Stored enablement is preserved. |
The action dialog is authoritative for the resource you are changing. Do not assume every resource has the same retention or restore behavior.
Resolve dependencies first
Active calculated variables cannot keep using an input you are archiving. Reconfigure or archive dependent calculations first. A parent resource’s lifecycle can also make its children unavailable even when those children have not been individually archived.
Check anomaly targets and dashboard references after retiring instruments or variables. Review notification definitions before archiving contact groups or templates.
Restore carefully
Where Restore is available, SanSignal reuses the existing resource identity and checks its current parent and dependencies. Restoring a calculated variable requires a rebuild; review the recalculation run before relying on the new result.
Restoring an FTP pipeline exposes the enabled or disabled value it had before archiving. A previously enabled pipeline can therefore resume work when restored and its other requirements are met.
Organization external connections have distinct controls: disabling is reversible, while their archive flow has blockers and no restore endpoint. Use disable when your intention is a temporary pause. Affinity pipelines have their own capture, processing, and archive controls; see Affinity.
Permanent removal
Deletion controls for resources such as projects or organizations require special care and may have their own confirmation and administration flow. Review the affected resources and preserve any required data through the supported data access workflow before requesting permanent removal.