How to Debug a 429 Rate Limit Error in Make.com

Description and use

A 429 error in Make.com when calling Alibaba Cloud’s Qwen‑Turbo API was debugged by isolating the failing module, reviewing provider logs, pausing retries, checking for other traffic, and using delayed retries, clarifying the rate‑limit cause.

Problem

A Make.com workflow failed with a 429 Too Many Requests error when calling Alibaba Cloud’s Qwen‑Turbo API, despite earlier modules succeeding.

Outcome

By systematically isolating the failing module and interpreting the provider’s error details, the author avoided unnecessary changes and identified that the 429 error was due to exceeding the API’s request limit.

Workflow

• Open the failed execution history
• Identify the first module that failed
• Read the complete error response
• Check the API provider’s request logs
• Pause repeated requests while investigating
• Check for concurrent traffic and usage limits
• Make one targeted change
• Run a controlled test and verify downstream steps

Evidence

The HTTP module failed.

Source

The error was: 429 Too Many Requests

Source

You have exceeded your current request limit.

Source

Stop replaying the failed run

Source

Add retries carefully

Source