Refresh issue lock TTL
Refresh issue lock TTL - Rensei REST API operation reference.
AuthorizationBearer <JWT>Short-lived worker runtime JWT minted by the platform. Claims bind the worker, project, organization, registration, and scopes.
id*stringapplication/json- body
workerId*stringissueId*stringackedInject?stringDelivery id the runtime has applied. Exact replay is accepted; unknown, non-in-flight, or dead-lettered ids return 409.
deadLetteredInjects?array<>Terminal consumer refusals. These are failure evidence, never acknowledgements, and are replayed until a 2xx response.
items <= 128sessionClass?stringRuntime session class, such as interactive; retained for backward-compatible heartbeat context.
Settlement accepted and lock refresh attempted. Applied/dead-letter reports settle even when refreshed is false.
application/json- response
refreshed*booleanstop?booleanPresent when the shared session status is terminal and the runtime must stop.
inject?curl -X POST 'https://app.rensei.ai/api/sessions/string/lock-refresh' \ -H 'Content-Type: application/json' \ -d '{ "workerId": "string", "issueId": "string"}'{ "refreshed": true, "stop": true, "inject": { "deliveryId": "string", "text": "string", "kind": "memory", "turnId": "string" }}ACK inbox message (Redis XACK)
ACK inbox message (Redis XACK) - Rensei REST API operation reference.
Worker rejection of a pre-claimed session
Allows a worker to reject a pre-claimed session (e.g. host capacity changed, workarea refused, or daemon is draining). Releases the claim and re-queues the session preserving its original priority. The original `QueuedWork` item must be supplied so the platform can re-enqueue without losing fields.