• 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

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

Workflows have stopped running

Hi team, it looks like our workflows aren't running today and I can't work out why? The last workflow ran at 10pm (Brisbane time) yesterday and there have been several webhooks sent into Pabbly since, but none of our workflows have been triggered in Pabbly. All workflows seem to be turned on, and I can't see any other issues.
 

Neeraj

Administrator
Staff member
Hello,

This is just our assumption but it might be the possible reason which led to fixing your issue.

We recently upgraded our Nginx server to Openresty to extend our Nginx Server.

Earlier all the webhook responses that were sent back to your webhook caller were now sent back from OpenResty server.

There was some configuration issue where the success response that we are used to sent back to your webhook caller might not be sent back properly.

Your webhook caller might not be receiving a notification from our side that we are able to already capture the webhook that they sent and they might not be sending any more webhooks considering they thought that we are not able to capture the webhooks.

We have resolved this config issue yesterday and I think this might be the reason for your issue.

Please note, this is the only possible reason that I can think of. We havent updated any thing else from our side in the last 24 hours.
 
Top