Clear a test's flaky mark
Requires the Flag tests permission.
Clears a flaky mark set by hand and returns the test with manualFlag null. Takes no body. A monitor still classifying the test keeps its status. Unmarking a test that is not marked changes nothing and returns it as it is.
The mark is not a status override. It counts as one more monitor classifying the test as flaky, so status is reconciled across every active monitor and a monitor classifying the test as broken still wins. The answer is the test after that reconcile.
A status change this causes sends the same customer webhooks as one made in the web app or by a monitor. That is deliberate: a consumer must hear about every status change, whatever made it.
A collection whose settings let only admins flag tests as flaky refuses anyone else with INSUFFICIENT_PERMISSIONS. An API token made on the API Keys page passes that check, since only an admin can make one or give it this permission; the organization’s legacy API token does not, since every member can see it.
The change is recorded as made by the API token, or by the person whose token made the call.
A 500 INTERNAL_ERROR says in its message whether the test was put back as it was. A 503 TEST_UNAVAILABLE means the change was made but the test could not be read back in time; read it with GET /v2/tests/{testId} rather than treating the change as failed.
Idempotency-Key is not honored. The change is idempotent by state, so a request whose outcome is unknown (a 504 or a dropped connection) is safe to send again.
A test in another organization is reported as 404, not 403.
Authorizations
An API key, sent as Authorization: Bearer <key>. An organization admin creates one in the Trunk app under Settings → Developer → API Keys and chooses the permissions it holds. A key with none can read merge queues but change nothing in them. Permissions cover merge queues and test-result uploads, including the quarantine lookups a CI run makes before it uploads; any key can call the other Flaky Tests and Dynamic CI endpoints, including their writes.
Path Parameters
Response
The test, after the reconcile
When the test's current quarantine began, as far as Trunk records it. Null exactly when quarantineState is notQuarantined. For a test quarantined by an alwaysQuarantine override, the time that override was set. For a test quarantined automatically, the later of statusSince and the last time an override on it was cleared. Changes to the collection's quarantine settings are not recorded per test, so this can be earlier than when quarantining was turned on for the collection.
"2026-06-01T10:00:00.000Z"