microsoft/autogen · error · Error

Failed to update session

Error message

Failed to update session

What it means

Thrown by SessionAPI.updateSession when PUT /sessions/{id}?user_id=... returns falsy status. It re-injects id and user_id into the body and PUTs the whole object; failures commonly stem from the session not existing/owned, or the updated payload failing backend validation.

Source

Thrown at python/packages/autogen-studio/frontend/src/components/views/playground/api.ts:72

    userId: string
  ): Promise<Session> {
    const session = {
      ...sessionData,
      id: sessionId,
      user_id: userId, // Ensure user_id is included
    };

    const response = await fetch(
      `${this.getBaseUrl()}/sessions/${sessionId}?user_id=${userId}`,
      {
        method: "PUT",
        headers: this.getHeaders(),
        body: JSON.stringify(session),
      }
    );
    const data = await response.json();
    if (!data.status)
      throw new Error(data.message || "Failed to update session");
    return data.data;
  }

  // session runs with messages
  async getSessionRuns(
    sessionId: number,
    userId: string
  ): Promise<SessionRuns> {
    const response = await fetch(
      `${this.getBaseUrl()}/sessions/${sessionId}/runs?user_id=${userId}`,
      {
        headers: this.getHeaders(),
      }
    );
    const data = await response.json();
    if (!data.status)
      throw new Error(data.message || "Failed to fetch session runs");
    return data.data; // Returns { runs: RunMessage[] }

View on GitHub (pinned to 027ecf0a37)

Solutions

1. Check data.message for the exact backend reason
2. Re-fetch the session first and 404-guard before updating (see exampleFix)
3. If it was deleted concurrently, recreate instead of updating
4. Align payload fields with the current backend Session schema

Example fix

// before
await sessionAPI.updateSession(sessionId, sessionData, userId);
// after
const existing = await sessionAPI.getSession(sessionId, userId); // throws with clear message if gone
await sessionAPI.updateSession(sessionId, { ...existing, ...sessionData }, userId);

null

try {
  await sessionAPI.updateSession(sessionId, sessionData, userId);
} catch (e) {
  if (/not found|does not exist/i.test(String(e))) {
    // deleted concurrently — recreate from current data
    await sessionAPI.createSession(sessionData, userId);
  } else throw e;
}

When it happens

Trigger: PUT /sessions/{sessionId} on a deleted session or one owned by another user_id, payload with fields the backend schema rejects, or concurrent deletion racing the update.

Common situations: Two tabs editing the same session, one deletes it and the other's save fails; session restored from stale state after backend DB reset; renamed/removed fields in the backend Session model after upgrade.

Related errors

• Failed to fetch sessions
• Failed to fetch session
• Failed to create session
• Failed to fetch session runs
• Failed to delete session

AI-assisted analysis of microsoft/autogen@027ecf0a37 (2026-08-15). Data as JSON: /api/errors/1561bf4567f25fd3. Report an issue: GitHub.