Optionalresult: {OptionalagentRun?: { ErrorMessage?: string }OptionalerrorMessage?: stringOptionalrequestAcknowledged?: booleanTrue when the fire-and-forget mutation returned an ACK before the transport died. False when the request never left the browser (or the ACK never arrived). Undefined for callers that do not know.
True when the failure text means the HTTP/WebSocket path died but the server-side AIAgentRun may still be Running. Painting Status=Error in that case leaves the Explorer timer stuck on In-Progress while the bubble says failed.
Does not match raw
Failed to fetch/NetworkError— those also fire when the initial mutation never reaches the server (no run exists). The GraphQL client rewrites a post-ACK disconnect to the "lost connection / still be running / please refresh" copy; only that copy (or an explicitrequestAcknowledged: true) is treated as in-flight.