Run once fails on all scenarios – temp_blueprint_instances_per_tx_position_seq reached maximum value

:bullseye: What is your goal?

I want to understand why Run once is failing on all my scenarios and find a way to restore manual executions.

:thinking: What is the problem & what have you tried?

Hi,

I’m currently unable to manually run any of my scenarios using “Run once”.

Every time I try to start a scenario manually, Make immediately returns the following error:

nextval: reached maximum value of sequence “temp_blueprint_instances_per_tx_position_seq” (2147483647)

The issue affects all scenarios that I try to launch manually, not just one specific scenario.

What is strange is that my automatically triggered/active scenarios are still working normally. The problem only seems to occur when I use Run once from the scenario editor.

The error appears before any module is actually executed, so it does not seem to be related to a specific app, connection, or module.

For example, one of the affected scenarios is a simple flow:

Tally webhook → HubSpot contact update → HubSpot note creation

My Make zone is:

eu2.make.com

From the error message, it looks like an internal PostgreSQL sequence used by Make has reached the maximum value of a 32-bit integer (2147483647), possibly while preparing or instantiating the scenario blueprint for a manual execution.

Has anyone experienced this issue before?

Is there any workaround to restore Run once, or is this something that needs to be fixed on Make’s infrastructure side?

Thanks for your help.

:clipboard: Error messages or input/output bundles

nextval: reached maximum value of sequence “temp_blueprint_instances_per_tx_position_seq” (2147483647)

Make’s performance is degraded at the moment: https://status.make.com/