• Instructions to Ask a Question

    For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.

    We offer seven comprehensive applications designed to help you efficiently manage and grow your business:

    Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.

    🚀 Exclusive Lifetime Offers 🚀

    We invite you to take advantage of our special one-time payment plans, providing lifetime access to select applications:

    • 🔥 Pabbly Connect — Lifetime Access for $249View Offer
    • 🔥 Pabbly Subscription Billing — Lifetime Access for $249View Offer
    • 🔥 Pabbly Chatflow — Lifetime Access for $249View Offer

    Make a one-time investment and enjoy the advantages of robust business management tools for years to come.

Pabbly Api error

Your Task History ID
IjU3NjIwNTY5MDYzMzA0MzA1MjY1NTUzNzUxMzM1MTZhNTQzOCI_3D_pc
Dear Pabbly Connect Support Team,

I hope this message finds you well.
I am reaching out to address a recurring issue I've encountered with my Pabbly Connect workflow. Recently, during the execution of certain workflows, I have been receiving an error message with the code
{
"response": "<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body>\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx/1.18.0 (Ubuntu)</center>\r\n</body>\r\n</html>\r\n"
}
. This error interrupts the automation process I depend on for my daily operations.
In an effort to resolve this matter efficiently and prevent future occurrences, I kindly request your guidance and support. If there are any recommended troubleshooting steps or best practices that I can implement to avoid this error, please provide them in detail.
Additionally, if this error code is indicative of a specific problem within my workflow setup or a system-wide issue, I would appreciate any insights you can offer. Clarification on what triggers this error and any potential fixes would be extremely valuable.
Thank you for your prompt attention to this matter. I look forward to your response and a resolution that ensures the smooth functioning of my workflows going forward.

Best regards,
 

ArshilAhmad

Moderator
Staff member
Hi @Abdulla Khalifa,

Based on the Task History ID you shared, it seems like the failed task was re-executed, and upon re-execution, it worked correctly, and you received a successful response. Because of this, currently, I won't be able to deduce the exact issue you faced with your initial execution of the task.
1701969500561.png

I suggest you monitor your workflow for some time, and if you encounter this error again, please let us know.
 
Top