Redispatch an outbox entry
Resets the terminally-INVALID transactional-outbox row back to PENDING for the request tenant so the relay dispatcher republishes it on its next tick. The row id is PRESERVED (the event is never recreated). Idempotent: a row that is not INVALID is left untouched and returns redispatched=false with its current status — a PUBLISHED row is never re-sent. An unknown id → 404. Multi-tenant is not yet supported → 501 (single-tenant only until outbox schema alignment). RBAC: outbox:redispatch; tenant is always derived from the validated request identity, never a path or payload value.
Authorizations
JWT bearer token issued by the identity provider.
Path Parameters
Outbox entry id. An unknown id is 404.
"ob-1"
Response
OK
Outbox entry id (preserved across redispatch; the event is never recreated).
"018f8a3e-4b2c-7c1a-9e5d-2f6a1b3c4d5e"
True when a terminally-INVALID row was reset to PENDING; false when the row was left untouched.
true
Outbox row status after the operation.
"PENDING"

