Decide what to do with the executions that were paused while the automation’s circuit breaker was tripped. Idempotent.
Documentation Index
Fetch the complete documentation index at: https://conductorone-groman-network-requirements-updates.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
This API uses OAuth2 with the Client Credential flow. Client Credentials must be sent in the BODY, not the headers. For an example of how to implement this, refer to the c1TokenSource.Token() function.
The unique identifier of the automation whose paused executions should be resolved.
The ResolvePausedAutomationExecutionsRequest message.
Whether to run or cancel the paused executions.
PAUSED_EXECUTION_DECISION_UNSPECIFIED, PAUSED_EXECUTION_DECISION_RUN, PAUSED_EXECUTION_DECISION_CANCEL Optional human-readable reason for the resolution decision. Stored on the audit row (paused_run / paused_cancelled events) for post-mortem and compliance use. Surfaced in the FE as a required field on CANCEL so admins capture why bulk-cancellation happened. Up to 1024 bytes.
Successful response
The ResolvePausedAutomationExecutionsResponse message.
The number of paused executions that were attempted but failed to resolve (e.g., a transient Dynamo error during the per-execution mutate). Per-execution failures do not abort the run — the loop continues, the failures are recorded on the audit row, and the affected executions remain in PAUSED_BY_CIRCUIT_BREAKER state so a subsequent call can retry them. Always 0 in the happy path.
The number of paused executions successfully resolved by this call (transitioned to PENDING for RUN, TERMINATE for CANCEL). Paused executions are processed inline, paginated server-side. For very large paused sets (10K+) this RPC may take seconds to minutes; callers should treat the request as long-running.