Issue Review: cloudflare/workers-sdk#2794

Summary

Wrangler randomly throws "Received a malformed response from the API" errors (502/504/524) when publishing pages.

Findings

• Created: 2023-02-24
• Updated: 2025-10-30
• Version: wrangler 2.1.13 → 4.61.0
• Component: wrangler, pages, api
• Labels: bug, pages, api
• Comments: 6

Key Evidence

• Random 502/504/524 errors from various API endpoints:
  • GET /accounts//pages/projects//upload-token -> 502
  • POST /zones/*/workers/routes -> 504
  • GET /accounts//pages/projects/ -> 504
  • GET /user -> 524
• Errors are intermittent - same command works on retry
• Maintainer @jahands acknowledged: "We should add retries to this API call"
• Some occurrences correlate with Cloudflare API incidents
• Users requesting configurable retries
• Issue persists over 3+ years

Recommendation

Status: KEEP OPEN

Reasoning: Valid UX issue - transient API errors cause deployment failures. The Cloudflare API occasionally returns 5xx errors that would succeed on retry. Adding retry logic (similar to what exists elsewhere in wrangler) would improve reliability significantly, especially for CI/CD pipelines.

Action: Implement retry logic with exponential backoff for Pages deployment API calls. Consider making retry configuration customizable (env var or flag).

Suggested Comment

This issue is about API reliability and retry handling. The Cloudflare API occasionally returns transient 5xx errors. Adding retry logic to Pages deployment commands would significantly improve the developer experience, especially in CI/CD environments.

Workaround: Wrap wrangler commands in a retry loop in your CI/CD scripts.