Nexla now automatically archives flows inactive for 60+ days to optimize platform performance and resource allocation.
What's New
Flows that have had no data processing activity for 60+ days will be automatically moved to an Archived state.
- Archived flows remain visible in the UI and retain their full configuration (sources, transforms, destinations, mappings)
- Flow state is preserved, so restored flows can resume normal operation immediately
- While archived, the underlying runtime resources are cleaned up, meaning the flow will not consume compute or infrastructure
- Archived flows display with a clear "Archived" badge in the flow list
Archival Criteria
- Any flow that processes records within the 60-day interval will not be archived. This also includes scheduled flows (quarterly, bi-annual, or annual runs) and any flows with intermittent but active data processing
- No data or configuration is deleted as part of this process
- All historical run data and logs remain accessible
Restoring Archived Flows
Flows can be restored through the Nexla UI or automatically via API:
1. Manual Restoration using Nexla UI:
- Navigate to your Flows page
- Locate the flow marked with "Archived" badge
- Click the flow's menu (•••) and select "Restore Flow"
- The flow returns to active state with all configurations intact
2. Automatic Restoration using Nexla API: Archived flows are automatically restored when flow or source activation calls are executed programmatically.
This change reduces unnecessary background activity, improves system reliability, and ensures resources are focused on active workloads—without impacting user ability to resume work when needed.