Table: make_scenario_dlq
If a scenario terminates unexpectedly because of an error, then the scenario run is discarded. You can set the scenario to store the failed scenario run as an Incomplete Execution. With that, if an error occurs in your scenario, you can resolve it manually and avoid losing data.
Key columns
- Provide a numeric
scenario_id
to query Incomplete Executions for a specific Scenario. This can be either set directly in awhere
clause, or specified as part ofjoin
with another table.
Caveat
- Be careful when requesting all columns (
*
) or one of the below-mentioned columns without using anid
in the query. To load this data, Steampipe will have to make one extra API request per Incomplete Execution returned:index
,deleted
,execution_id
,scenario_id
,scenario_name
,team_id
,team_name
Examples
List of all Incomplete Executions
select *from make_scenario_dlqwhere scenario_id = 1;
List all unresolved Incomplete Executions
select id, reason, attempts, createdfrom make_scenario_dlqwhere scenario_id = 1 and resolved = false;
Schema for make_scenario_dlq
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form, e.g. connection_name. | |
attempts | bigint | Number of attempts. | |
created | timestamp with time zone | Date and time when this Incomplete Execution was created. | |
deleted | boolean | Was the Incomplete Execution deleted? | |
execution_id | text | The execution ID. | |
id | text | = | The Incomplete Execution ID. |
index | bigint | Incomplete Execution index. | |
reason | text | Description of the problem. | |
resolved | boolean | Was the Incomplete Execution resolved? | |
retry | boolean | Retry triggered? | |
scenario_id | bigint | = | The Scenario ID. |
scenario_name | text | The Scenario name. | |
size | bigint | Data size of the bundle stored in the Incomplete Execution in bytes. | |
team_id | bigint | The Team ID. | |
team_name | text | The Team name. |