-
Notifications
You must be signed in to change notification settings - Fork 276
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:
- Are intermittent 502s expected from the MCP gateway?
- Do MCP endpoints support Retry-After headers?
- Is there an official recommended retry + backoff policy for MCP?
- 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
Labels
No labels