Workflows
List a debug attempt's history
Read an attempt and your earlier attempts of the same node.
GET
List a debug attempt's history
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.
v2 compatibility notes
GET /api/v2/workflows/listDebugAttemptHistory
Returns the attempt and your earlier attempts of the same node, newest first, without their snapshots or outputs, a page at a time. The first page starts with the attempt itself. An earlier attempt whose source run carries a company your key cannot read is left out, as getDebugAttempt answers it 404, so a page may hold fewer attempts than limit while more remain. Use compareDebugAttempts to see two side by side.
Authentication
Personal key, External App credential or platform API key. Requires permissionworkflows:use, and the credential’s scopes must also reach workflows:read (a 403 naming it otherwise). Both are decided at the workflow’s home org unit. A debug attempt is personal, as in the Console: you debug drafts you created and read attempts you started. With a Personal key that is its owner; an External App or a platform key is its own creator (externalApp:<id>, apiKey:<id>). When draft debugging (workflow_debug_execution) is off for you (a Personal key’s owner) or for the deployment (an app or platform key), the route answers 409 conflict.
Query parameters
Responses
200 with data.items and data.retentionExpiresAt. While meta.hasMore is true, pass meta.nextCursor as cursor with the same id; the cursor starts d1. and is bound to this operation, id and the credential. The list never answers meta.partial.
Errors
Example
Authorizations
Path Parameters
Query Parameters
Response
The node's attempts

