Setting how many webhooks can be processed in parallel
planned
Pierre Becher
We sometimes have the problem that too many webhooks arrive at the same time, so that the scenario gets processed 50 times in parallel, which results in hitting rate limits of the ClickUp API. We could instead use "Sequential processing" but then only one would be processed at a time, which slows down the process massively.
We would like to suggest an option in each scenario to set X amounts of webhooks can be processed at a time.
For some scenarios I would like to process 10 in parallel, for others maybe only 5 in parallel.
Is this porrible to implement?
Thanks.
Log In
Mayank Chhotwani
upvote
Conor Power
Hello! This one is super important.
Whilst MAKE can quite easily handle 50 runs in parallel - almost every other 3rd Party Service can not, and it will cause Rate Limiting issues via their API.
This has grown to be more of an issue in the past 12 months where the number of parallel runs seems to have increased. Most notable when you have an error and a scenario then switches off. It can lead to 100s if not 1000s in a queue, that will be processed in parallel when you switch back on.
In an ideal world, we'd like to be able to set the maximum number of parallel executions by scenario/webhook. As a "starter for 10", if we could set a maximum on an organization level e.g. "maximum of 10 parallel runs per scenario," then that would be a big help whilst the functionality to set per scenario is worked on.
Thanks!
Ondřej Veselý
planned
Hello, our team is currently working on a solution that will solve this problem with hitting limitations on 3rd party applications. I will provide an update once the feature is ready.
Brisbane Markets Limited
Ondřej Veselý: This will be great, as we're also hitting API limits with Microsoft Business Central. Can't wait!
Arnoud Post
Ondřej Veselý Any news on this?
Arnoud Post
Ondřej Veselý ?