Dark Mode

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Intermittent 502 Bad Gateway errors from MCP endpoint under moderate call volume (no retry guidance) #104

Open
Open
Intermittent 502 Bad Gateway errors from MCP endpoint under moderate call volume (no retry guidance)#104

Description

Hi Bright Data team,

We're using the Bright Data MCP in an agent-based workflow (via n8n).
Under moderate load (~100 MCP calls per workflow run), we occasionally receive:

502 Bad Gateway responses (HTML error page from gateway)

The error is rare per-call, but statistically guaranteed at scale.
There is currently no documented retry / backoff guidance specific to MCP usage.

Questions:

  1. Are intermittent 502s expected from the MCP gateway?
  2. Do MCP endpoints support Retry-After headers?
  3. Is there an official recommended retry + backoff policy for MCP?
  4. Are there known concurrency or rate limits specific to MCP usage?

This is not a routing issue on our side -- MCP dynamically selects endpoints/params as designed.

Thanks in advance -- guidance here would help make MCP reliable at scale.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions