Hi @vishalnomula 
It’s been a while since you posted this, so I’m guessing you might’ve already solved it. If so, we’d love to hear about the solution you implemented—it could really help others running into the same issue. 
If it’s still erroring, you might want to try adjusting the Delay action. Looks like the Zap is using a Delay For action, which means if your Zap is triggered multiple times simultaneously, the final action will be delayed by the same amount in each run. Instead, you can try using a Delay After Queue action, which staggers the running of any actions that follow it. You can learn more about that here: Delay after queue.
Alternatively, if the issue is more that the Zap is hitting the app’s API rate limits due to retrieving too many clients at once, you might want to try reducing the number of clients each webhook pulls as well as adding Delay actions between the Webhooks actions to help avoid them running too closely together.
Keep us posted on how it’s going, want to ensure this gets sorted! 
Hi @vishalnomula
Here’s a tip to try for a different execution configuration:
Use 1 Code step that iterates to do pagination and handle the data results and output response however you want.
That will use 1 Task instead of N Tasks for each Webhook step.
Ask ChatGPT for help converting the API request to be done in a Code step. (JavaScript or Python)
Code help: https://zapier.com/apps/code/integrations#help
Hey @vishalnomula, just wanted to check on your progress here. Were you able to get this sorted?
Let us know if you still need any help at all!