Member Junction
    Preparing search index...

    Function IsDisconnectWhileAgentMayStillBeRunning

    • 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 explicit requestAcknowledged: true) is treated as in-flight.

      Parameters

      • message: string
      • Optionalresult: {
            agentRun?: { ErrorMessage?: string; Message?: string; Status?: string };
            errorMessage?: string;
            requestAcknowledged?: boolean;
        }
        • OptionalagentRun?: { ErrorMessage?: string; Message?: string; Status?: string }
          • OptionalErrorMessage?: string
          • OptionalMessage?: string

            The agent's own last message. When the run is awaiting a human this is the question it is waiting on — not an error.

          • OptionalStatus?: string

            The persisted AIAgentRun status. Widened to string on purpose: this module is the arbiter for results arriving off the wire, where the value is whatever the server wrote, and a literal union here would reject a run carrying a status this build does not know about instead of letting the checks below decide.

        • OptionalerrorMessage?: string
        • OptionalrequestAcknowledged?: boolean

          True 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.

      Returns boolean

    Settings

    Member Visibility