• 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 workflow randomly firing multiple times with only one input. NEED FIX ASAP!

As other users have pointed out, there is something going on with Pabbly right now.

With my workflow, a cusomer should be created and a SINGLE invoice sent.

Tonight, I have had over 7 customers receive anywhere between three to FIVE invoices from one single order (workflow). This is not only embarrasing, it's causing serious financial headaches and accounting errors.

For the record: I haven't TOUCHED this workflow in months. Months.
This began happening randomly today, which is how I know it's not an error on our part with Pabbly's software.

This is one of many major issues with Pabbly I've had lately.

Picture for example:

delete later2.png


You can see how the same cusomer receives multiple duplicate invoices, some of which are an HOUR after their first one. Why is Pabbly doing this?!
 
P

Pabblymember11

Guest
The reason is a webhook retry. If the destination is not accessible. Multiple attempts are made by the source application (RazorPay/Shopify etc) to submit the webhook.

Although it was occasionally accepting the webhook when our webhook destination was slow, it was unable to notify RazorPay that we had received the message.

As a result of Razorpay not receiving the acknowledgment. In an effort to get our attention and get the information across, it kept trying and sending webhooks again.
 
Top