Un-park operations held by a permanent forward rejection
Clears the outbound transmit claim of the named operations, returning them to the eligible backlog so the next forward tick re-drives them. RBAC: connectivity:admin. It is the ONLY recovery path for an operation PARKED after Núclea permanently rejected its forward file (400/422): a parked operation stays ACCEPTED with its transmit claim held, which makes it invisible to every drain and to /retransmit, /advance, /requeue and /retry. Supply the operation ids the operation.forward_rejected alert reported (payload operationIds, mirrored in the park’s ERROR log field parked_operation_ids) — there is no scope-wide form, because a held claim cannot distinguish a parked operation from one whose file is already on the wire. Idempotent: re-running releases nothing further and reports released=0. Claims younger than the 5-minute safety floor are skipped (they may belong to a pass that is mid-submit). Runs lock-free: it transmits nothing.
Authorizations
JWT bearer token issued by the identity provider.
Body
Parked operation ids to un-park, as reported by the operation.forward_rejected alert (payload operationIds) or the park's ERROR log field parked_operation_ids. 1..500 UUIDs.
Response
OK
Recovery action that was executed.
"unpark"
Transmit claims actually cleared; these operations are back in the eligible backlog.
2
Distinct operation ids named in the request.
3
Ids that carried no transmit claim (never parked, or already un-parked) or whose claim is younger than the safety floor.
1

