API Limit Errors

[AbsoluteAutomations]

Your Workflow URL

https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTZiMDYzMTA0M2M1MjZlNTUzMzUxMzEi_pc

Your Task History ID

https://connect.pabbly.com/task/history?filter_status=applied&filter_by_workflow_id=IjU3NjYwNTZiMDYzMTA0M2M1MjZlNTUzMzUxMzEi_pc#

Consent to Access & Modify

I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.

Hey team, I'm hoping for your help with failures occurring on this workflow please - https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTZiMDYzMTA0M2M1MjZlNTUzMzUxMzEi_pc

The workflow is triggering once a week for approx 85 records at once, where there is a GET request being sent to Ontraport, to get data and that step is failing due to - API concurrency limit exceeded. Please try again later.

I've reached out to Ontraport Support and they recommended that we ask you to increase our API limit. They explained on their end, their API should be able to accept these calls without any limit being exceeded.

Looking forward to hearing from you

 

[ArshilAhmad]

Hi @AbsoluteAutomations,

Could you please share the cURL command and the API documentation for the endpoint you are trying to execute?

 

[AbsoluteAutomations]

Hi Arshil, sure thing, here are the Ontraport API docs - https://api.ontraport.com/doc/#objects

You can see the exact failure and endpoint on this example - https://connect.pabbly.com/task/his...d=IjU3NjYwNTZiMDYzMTA0M2M1MjZlNTUzMzUxMzEi_pc

 

[Soumya Tripathi]

Hello @AbsoluteAutomations
We have forwarded the issue to the technical team, and they will investigate the problem you are facing. Please allow us some time.

 

[AbsoluteAutomations]

Thank you Soumya for your reply. I'll stand-by on this end.

 

[Soumya Tripathi]

Hello @AbsoluteAutomations
As we checked, the workflow is sending a large volume of data at once without any delay between the requests. To help resolve this, we recommend adding an additional action step “Delay After Queue” to introduce a gap between requests.

Additionally, the error “API concurrency limit exceeded. Please try again later” is coming from Ontraport, which you are accessing via API by Pabbly. We suggest reaching out to the Ontraport team for further clarification regarding their API limits.

This adjustment should help reduce the failures, and the Ontraport team can confirm if any further changes on their end are required.

 

[AbsoluteAutomations]

Thanks Soumya for your reply. The OP team have already explained that their API can handle the requests and they should not be erroring, so that's why they asked that we speak to you about this, hence the creation of this ticket. So now I'm kinda stuck in the middle unfortunately, if both sides are asking me to talk to the other.

Regarding the 'Delay After Queue' action, can you share how this can be added to the current build? And does this mean that you'll progressively release the records running through?

 

[Soumya Tripathi]

Hello @AbsoluteAutomations
As mentioned previously, the error “API concurrency limit exceeded. Please try again later” is coming from Ontraport, which you are accessing via API through Pabbly. Since this application is not natively integrated and you added it via API by Pabbly, we recommend reaching out to the Ontraport team for clarification regarding their API limits. You can also share a screenshot of this response with them.

Additionally, to reduce the likelihood of hitting this limit, you can add a Delay step before the API action. This will process the data in intervals, allowing the next action step to run smoothly.

 

[AbsoluteAutomations]

Thanks Soumya for your feedback here, I have shared this with the team from Ontraport and will be back in touch soon.