Hi, I’m currently working on editing an automation and encountered this message: “You have hit the limit of 50 logic blocks for an automation.” I believe this limitation could pose a risk if larger workflows are being planned. I’d like to request an increase to this limit.
I think this should follow microservice principle : Splitting up your larger workflows increase transparency and maybe performance especially if you have more than n decisions in your flow.
1 Like
Thank you for the feedback, Edgar. Let me connect with the team and circle back. Part of the reason we have the 50 automation block and 60 second limits per run, is as Tobias mentions having smaller automations gives more control and visibility.
However, we acknowledge there are cases where the ability to create a larger Automation could be useful.
Could you give us a bit more insight into your use case, and also what number of blocks you feel would be a good limit for your team?
- Olga
Thank you for your message. I appreciate your understanding of our needs.
I completely understand the rationale behind the 50 automation block and 60-second limits, as smaller automations indeed provide better control and visibility.
In my case, I ended up finding another way to achieve our goals with fewer logic points, and I also opted to create several automations rather than focusing everything into one. This actually does not represent a blocker for us, as we continue to explore this option. So far, we have only used it to automate certain KPIs without the need to alter or modify our applications.
Thank you again for your support
1 Like
Hi folks - we’re considering increasing the Automation block limit to 100 (from 50).
Would that be helpful?
2 Likes
Totally!
How long that will take?
We’re trying to fit it into the next sprint. I’ll update here if we do. Otherwise, hoping for next month or two.
1 Like
The limit for automation blocks has been increased from 50 to 100 in Platform Release 300 - January 2025 
1 Like