Skip to content

circuit breaker error when restart 1.0.7 #2149

Closed as not planned
Closed as not planned

Description

@XJTLUmedia

Describe the bug

All MCP connection in error, and this triggered. I have no idea why
Image
I am not able to update, and all connection seems to lost

Affected version

No response

Steps to reproduce the behavior

No response

Expected behavior

It should be no problem

Additional context

When I trying to open Copilot 1.0.7 using copilot --resume

Activity

  1. added theissue type on Mar 19, 2026
  2. added
    area:mcpMCP server configuration, discovery, connectivity, OAuth, policy, and registry
    and removed on Apr 16, 2026
  3. patniko commented on Oct 26, 2026

    @patniko
    Collaborator

    Thanks for the report. We couldn't investigate from the screenshot alone, and MCP connection handling has changed a lot since v1.0.7 — for example, remote MCP connections retry on transient network failures (v1.0.25), MCP failure warnings include the server's stderr output (v1.0.42), and MCP tools recover more reliably from transient connection failures (v1.0.88). Please update to the latest version (v1.0.103) with copilot update or your package manager; if you still see the circuit-breaker error, open a new issue with your CLI version, the exact error text, your MCP server configuration (secrets redacted), whether it only happens with --resume, and debug logs (--log-level all --log-dir <dir>).

    Triaged as part of a Copilot SDK backlog review, with help from GitHub Copilot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:mcpMCP server configuration, discovery, connectivity, OAuth, policy, and registry

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions