Important Latenode Platform Update 
Here’s what changed on the platform — and why it matters for you.
How it used to work
Every plan had a limit on parallel executions. When more events arrived than the limit allowed, new requests received a 429 error and were simply dropped. We know this caused problems for many of you — and now it’s a thing of the past.
How it works now
You can send an unlimited number of events to your scenarios — all of them will be processed. Latenode dynamically scales workers based on load, and requests are queued and handled as resources become available.
Processing priority depends on your plan:
- Free plan — lower priority (events are still processed, but may take a bit longer during high load)
- Paid plans — higher priority: the higher your plan, the faster your queue moves
Reserved Workers
If you need guaranteed capacity for a specific project — regardless of overall system load — you can add reserved workers. They are tied to your account and always available for your scenarios. To get started, contact us at [email protected].
Per-scenario execution mode
You can now choose an execution mode for each scenario — sequential or parallel with a configurable limit. This helps avoid race conditions when multiple simultaneous runs compete for the same data.
Learn more about parallel execution limits
Fast mode for webhooks
If an external service expects a quick response and may drop the connection before your scenario finishes — we built Fast mode for this: the webhook responds instantly while the scenario continues running in the background. Perfect for integrations with timeout-sensitive systems.
Learn more about async webhook mode
Do you need to do anything?
Nothing. If your scenarios ever hit the execution limit — that won’t happen anymore. The update has already been applied to all accounts automatically.