Account is temporarily blocked due to exceeding request limit

Beginner Questions
1

:bullseye: What is your goal?

i am currently trying to complete the make academy foundations course.

:thinking: What is the problem?

i have gone to run my scenario, however i’m receiving this error:
nextval: reached maximum value of sequence “temp_blueprint_instances_per_tx_position_seq” (2147483647)

i have also received an email saying; '‘429: your account is temporarily blocked due to exceeding of request limitation of your subscription type.’

:test_tube: What have you tried so far?

tried support but no luck. free plan.

:camera_with_flash: Screenshots: scenario setup, module configuration, errors

Screenshot 2026-08-24 at 12.50.55.png
Screenshot 2026-08-24 at 12.50.55.png2024×1054 216 KB

4

Hi Umar,

That is a rough place to get stuck during the Foundations course. The screenshot shows two separate errors, and the first one appears before your Weather, Router, or Google Sheets modules start.

In the run log, the sequence error appears immediately after “Requesting execution”. The number 2147483647 is the maximum value of a signed 32 bit integer. Together, that points to a backend sequence reaching its configured limit during Make’s execution setup, not a module setting you can change.

There is one useful check before you go back to support. Make reported an EU2 incident on August 24 called “Issues with Scenario saving and Execution on EU2”. Its status updates ran from 13:36 to 13:46 CEST, and it made manual scenario runs fail. If your browser address starts with eu2.make.com, compare the failed run time with that window.

Treat the 429 email as a separate issue. It says the account hit a request limit for its plan, but the screenshot does not show that the sequence failure retried or caused that limit. Do not keep pressing Run once while the temporary block is active. Compare the email time with your manual attempts and any scheduled runs.

If the time and region match the resolved incident, try Run once a single time after the temporary block clears. If they do not match, or the sequence error returns, send support the exact nextval message, the screenshot, the scenario URL or ID, the organization ID, and the failed run time. Ask them to escalate the backend sequence error to engineering and investigate the 429 separately. I would not rebuild the scenario or upgrade the plan to test an error that happened before any module ran.

5

Hey there,

there was an outage yesterday, maybe it was related to the issue you had. Is the problem still occurring?