api failure?
Status: Open · Asked by Gabe Monroy on · 0 views
I am having failed api tasks see screenshot
Attachments
Hi @monroy330,
Could you please share the Workflow URL in which you have this concern?
Please click on the 'Capture Webhook Response' button and make a submission by adding a new tag.
Then map the details captured from GHL to the endpoint you are trying to execute and click on 'Save & Send Test Request'.
Yes that did work to do the test and get it connected. But....when I use this trigger I select all my contacts in GHL and add them to the workflow. I do not use the tag. This is actually working for me but sometimes I still get this error and i would like to know why? Here is the link to another flow that is working just fine but also giving me the error randomly - https://connect.pabbly.com/task/history?filter_status=applied&filter_by_task_id=IjU3NjMwNTZiMDYzZTA0M2M1MjZjNTUzMjUxMzQ1MTYwNTQzNyI_3D_pc
We tried to find a difference between a failed and successful execution of the endpoint, but weren't able to find any. The endpoint you are trying to execute seems to be failing randomly. Please get in touch with the application's support team to understand why it's failing as the issue seems to originate from their end.
What does this one mean?
{
"HTTP Status Code": 502,
"message": "The application processed the request but returned a blank response. Refer to the HTTP status code above for details."
}
https://connect.pabbly.com/workflow/mapping/IjU3NjUwNTY4MDYzZTA0MzI1MjZiNTUzMTUxM2Ei_pc
I am unable to see any HTTP Status Code 502 in the workflow you have share.
Could you please share the Task History ID of this execution?
Pabbly Connect waits for 25 seconds to receive a response from any application. The issue you are describing occurs when an application (Nifty) takes more than 25 seconds to process a request, and because of this, Pabbly Connect does not receive the response within 25 seconds, leading to this error. You can add a Delay as the 2nd step of your workflow to prevent this error.
I'm still getting a ton of errors like this: https://connect.pabbly.com/task/history?filter_status=applied&filter_by_task_id=IjU3NjMwNTZhMDYzNDA0MzQ1MjZiNTUzZDUxMzI1MTYwNTQzNSI_3D_pc
I don't understand why? I'm using GHL to add contacts to work flow in bulk instead of using the tag and when I test it works fine so why am I getting this weird error.
I'm still getting a ton of errors like this: https://connect.pabbly.com/task/history?filter_status=applied&filter_by_task_id=IjU3NjMwNTZhMDYzNDA0MzQ1MjZiNTUzZDUxMzI1MTYwNTQzNSI_3D_pcI don't understand why? I'm using GHL to add contacts to work flow in bulk instead of using the tag and when I test it works fine so why am I getting this weird error.
Please get in touch with your application's support team as the unprocessable_entity error seems to be coming from their end.
This is GHL. Are you saying I need to get in touch with their support? I have spoke to them and I don't get this error when I do the custom trigger they provide. I only get this error when I integrate with Pabbly. They are just going to tell me to talk to you guys since it is not their integration.
Is it a GHL endpoint you are trying to execute?
GHL is connected to pabbly to trigger the ai call to go out. the ai call is started from that endpoint. When I do the same connections in GHL with their premium webhook, it works fine.
You need to get in touch with the AI call application whose endpoint you are trying to execute, as the issue is related to that application.
I got it figured out. It was a voip number and endpoint was blocking that.
Thank you for the update. I am glad the issue is fixed now.