Update Metronome run

PATCH/v1/metronomes/{metronomeId}/runs/{runId}

Attach a run to a project or ticket for later review and filtering.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
metronomeIdpathstringYesMetronome workflow ID
runIdpathstringYes
Query parameters
None.

Body schema

Content type: application/json · Optional

FieldTypeRequiredDescription
attachedProjectIdstringNo
attachedTicketIdstringNo

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Metronome run updatedapplication/json
FieldTypeRequiredDescription
dataobjectNo
data.idstringNoUnique identifier.
data.metronomeIdstringNo
data.userIdstringNoUser ID.
data.triggerTypestringNo
data.versionIdstringNo
data.triggerEventIdstringNo
data.idempotencyKeystringNo
data.statusqueued | running | waiting_approval | paused | completed | failed | cancelledNoCurrent lifecycle status.
data.inputobjectNo
data.outputobjectNo
data.errorstringNo
data.startedAtstringNoISO 8601 timestamp.
data.queuedAtstringNo
data.nextAttemptAtstringNo
data.lockedAtstringNo
data.lockedBystringNo
data.attemptCountintegerNo
data.maxAttemptsintegerNo
data.timeoutMsintegerNo
data.attachedProjectIdstringNo
data.attachedTicketIdstringNo
data.completedAtstringNoISO 8601 timestamp.
data.createdAtstringNoISO 8601 timestamp.
data.updatedAtstringNoISO 8601 timestamp.
Update Metronome run
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow