UPupsmith
admin
admin

Diagnose Stuck State

Report whether this engagement is wedged on an orphan ext-mod write-ahead.

Matches the FatalError gate in agent-service/agent/runner/handler/run_requested.py: a stuck engagement has an EventAction.success IS NULL row AND a matching dangling ToolCallPart in the most recent persisted ModelResponse. When both hold the worker loops through DLQ on every retry.

get/admin/engagement/{engagement_id}/stuck-state

Request

  • Base URL
    https://api-docs.upsmith.com (the document declares no server; this is the origin it was published from)
  • Auth
    • API key in header x-api-key
    • or HTTP bearer

Path parameters

engagement_idstring required

Headers

organization-idstring nullable
timezonestring
x-user-idstring nullable
x-actor-emailstring nullable
x-request-sourcestring nullable
x-operation-idstring nullable
x-commit-messagestring nullable
x-confirmation-idstring nullable
x-chat-idstring nullable

Response

Successful Response

is_stuckboolean required

Changes

No recorded changes to this operation across all 1 revision of this API.