You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{"run":{"run_id":"<id>","agent_id":"<id>","state":"QUEUED","created_at":"2024-08-26T19:05:47.442Z","updated_at":"2026-08-22T09:50:35.176Z","pending_interactions":[{"interaction_id":"<id>","type":"TOOL_APPROVAL","display_name":"King.Trantow44","description":"provided collectivization whereas disapprove gah astride under stoop louse","arguments":{"key":"<value>","key1":"<value>"}}]},"request_id":"<id>"}
REQUEST_BOUND preserves the existing wait/stream behavior. DURABLE starts a fresh, persisted execution with a 30-minute execution timeout and returns immediately. DURABLE requires stream to be false or omitted and does not accept metadata.chat_session_id. It does not bypass tool approval requirements or provide automatic QE-crash resumption. Expiry is read-triggered: the next GET of the run marks an active turn FAILED if more than 40 minutes have passed since the turn was accepted. There is no periodic sweep, so the stored run can remain RUNNING until it is read. Expiry never replays execution or expires approval-paused runs, and failure does not prove that external tool work has stopped.
0 commit comments