Data Staging: Store and Re-ingest Last Execution Data
Applicable for: Non-UAI Connectors
Data Staging allows you to temporarily store raw, pre-transformed data retrieved from third-party APIs during a connector execution. When activated, the data is stored in a temporary storage with a 7-day retention period.
This feature helps you quickly recover from configuration or identification issues without re-fetching data from the source system.
Use Data Staging when:
- Asset identification rules were misconfigured during ingestion
- Connector configuration errors caused incorrect data mapping
- You need to reprocess the most recent execution without calling the source API again
How to Activate Data Staging
To enable Data Staging for a connection:
- Go to Connections.
- Select the connection you want to configure.
- Click Edit.
- Navigate to the Profile section.
- Select the Enable Data Staging checkbox.
- Save the connection.
When enabled, all incoming raw, pre-transformed data from the connector API is automatically staged.
Staged data is retained for 7 days from the time of ingestion.
How to Re-ingest Staged Data
If an error occurs during the connector run, you can re-ingest the last execution using staged data.
To re-ingest staged data:
- Go to Connections.
- Locate the required connection.
- Open the Quick Actions menu.
- Select Re-ingest Last Execution.
The system reprocesses the most recent execution using staged data instead of making new API calls to the source system.
Re-ingest Option Availability
- The Re-ingest Last Execution option is available only when Data Staging is enabled on the connection’s Profile page.
- If Data Staging is not enabled, the option does not appear in the Quick Actions menu.
Limitations
- Data Staging is supported only for Non-UAI (host-based) connectors
- Only the last execution is available for re-ingestion
- Staged data expires automatically after 7 days