What is an execution and what does execution.failed mean?

An execution is a single data fetch attempt that Catena runs on a schedule to pull data from a carrier's TSP. Each connection has one or more schedules (one per resource type, such as vehicle_location or hos_event), and each schedule runs executions at regular intervals.

An execution.failed webhook event means one of those fetch attempts returned an error from the TSP. A single failed execution is not necessarily a problem. Catena retries automatically and most transient errors (network timeouts, TSP rate limits) resolve on their own.

When to take action:

• If execution.failed events repeat continuously for the same connection and resource type, the carrier's TSP may have an account-level issue such as suspended credentials or a permissions change.
• If failures escalate to a schedule.deactivated event, data ingestion has stopped entirely and intervention is required. See article 3.8.
• If failures escalate to a connection.staled event, the carrier needs to re-authenticate. See article 3.6.

Execution history is available for 7 days via the List Executions endpoint. After that window, execution records are removed.