Get an Execution Endpoint Returned 404 Error: "That execution does not exist." While the Execution ID is Correct

Last Updated: Feb 20, 2026

Overview

The Management API Endpoint Get an execution (GET /api/v2/actions/executions/{id}) and returns a 404 error while the execution ID was valid.

That execution does not exist

The endpoint returned the execution data with the status code 200 on the retry.
Why were responses inconsistent?

Applies To

Error 404
Management API Endpoint

Cause

Some Management API endpoints do not guarantee immediate consistency. There can be a short delay before the execution data becomes available in API.

Solution

Retrying with exponential backoff might help. However, there is no guaranteed turnaround time. Please make sure the code gives up retrying at some point.