microsoft/autogen · error · Error

Failed to delete team

Error message

Failed to delete team

What it means

Thrown by TeamAPI.deleteTeam in the AutoGen Studio frontend when the DELETE /teams/{teamId}?user_id={userId} request either fails server-side or returns a payload whose status field is falsy. The method always awaits response.json(), so a non-JSON error body (e.g. an HTML 500 page) surfaces as a SyntaxError instead, while this message covers the explicit failure path. It indicates the team was not deleted.

Source

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

      method: "POST",
      headers: this.getHeaders(),
      body: JSON.stringify(team),
    });
    const data = await response.json();
    if (!data.status) throw new Error(data.message || "Failed to create team");
    return data.data;
  }

  async deleteTeam(teamId: number, userId: string): Promise<void> {
    const response = await fetch(
      `${this.getBaseUrl()}/teams/${teamId}?user_id=${userId}`,
      {
        method: "DELETE",
        headers: this.getHeaders(),
      }
    );
    const data = await response.json();
    if (!data.status) throw new Error(data.message || "Failed to delete team");
  }
}

// move validationapi to its own class

export class ValidationAPI extends BaseAPI {
  async validateComponent(
    component: Component<ComponentConfig>
  ): Promise<ValidationResponse> {
    const response = await fetch(`${this.getBaseUrl()}/validate/`, {
      method: "POST",
      headers: this.getHeaders(),
      body: JSON.stringify({
        component: component,
      }),
    });

    const data = await response.json();

View on GitHub (pinned to 027ecf0a37)

Solutions

1. Verify the team still exists and belongs to the passed user_id via the gallery/list endpoint before deleting.
2. Reproduce with curl: DELETE {base}/teams/{id}?user_id={uid} with X-Storage-Token header and inspect the JSON message field, which is preferred over the generic message.
3. Check the AutoGen Studio backend logs for the exception raised while deleting the team (often a DB/integrity error).
4. If the backend returns HTML error pages, response.json() throws before this message; fix the server error first.

Example fix

// before
const data = await response.json();
if (!data.status) throw new Error(data.message || "Failed to delete team");

// after (also handle non-JSON and HTTP errors)
const text = await response.text();
let data: any = {};
try { data = JSON.parse(text); } catch { /* non-JSON body */ }
if (!response.ok || !data.status) {
  throw new Error(data.message || `Failed to delete team (HTTP ${response.status})`);
}

// Confirm the team exists and is owned by the user before deleting
const teams = await teamAPI.getTeams(); // list call
const target = teams.find((t) => t.id === teamId);
if (!target) throw new RangeError(`Team ${teamId} not found; refresh the list`);

const isApiError = (e: unknown): e is Error & { message: string } =>
  e instanceof Error && /Failed to delete team/.test(e.message);

try {
  await teamAPI.deleteTeam(teamId, userId);
} catch (e) {
  if (e instanceof SyntaxError) {
    // response.json() failed: server returned non-JSON (likely HTML error page)
    console.error('Server returned a non-JSON error body');
  } else if (e instanceof Error) {
    // e.message is the server's message or 'Failed to delete team'
    showErrorToast(e.message);
  }
  // keep the row in the UI; do not remove it optimistically until success
}

When it happens

Trigger: Calling deleteTeam(teamId, userId) when the backend route rejects the deletion: team not found for that user_id, wrong user_id ownership check, backend exception (500), or an auth/proxy layer returning JSON with status:false. Note the method does not check response.ok, so 4xx/5xx bodies that still parse as JSON with no status field also trigger it.

Common situations: Stale teamId in the UI after another session deleted the team; user_id mismatch between logged-in user and the row's owner; API server restarted or database unavailable; running the frontend against a backend version whose /teams DELETE response shape differs (missing data.status).

Related errors

• Failed to validate component
• Failed to test component
• Failed to list MCP tools
• HTTP ${response.status}: ${errorText || "Failed to create We
• Failed to call MCP tool

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