Our Workflow is running twice since yesterday

[abhishek@tbn]

Hello Support,

All our workflows are running twice for every request can you please check and resolve it.

--Abhishek

 

[Preeti Paryani]

Hello @abhishek@tbn,

Could you please share the email address associated with your Pabbly Connect account, or provide the URL of any workflow that is running twice? This will help us investigate the issue and assist you more effectively.

The issue you're experiencing usually occurs due to multiple clicks on the "Save and Send Test Request" button, which could have led to Multiple triggers(data duplication). For more details, please refer to the attached image.

In such cases, we recommend setting up the workflow again from scratch and re-establishing the connection with the trigger step. Be sure to click the "Save and Send Test Request" button once.

 

[abhishek@tbn]

here is the Workflow url "https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTZmMDYzZjA0MzU1MjY4NTUzNzUxMzUi_pc" please check and resolve it ASAP.

 

[Preeti Paryani]

Hello @abhishek@tbn,

Upon reviewing your workflow, we noticed multiple duplicate entries, which appear to be causing the issue.

Please note that Razorpay triggers are descriptive, meaning the data sent by Razorpay is only visible under the Task History in Pabbly. Duplicate entries can occur due to the following reasons:

• The same webhook has been added multiple times in your Razorpay account.
• Razorpay is sending the same response more than once.

To troubleshoot this, we suggest:

1. Create a new workflow with a fresh webhook URL and test if it captures the response only once.
2. Check your Razorpay dashboard for any duplicate webhook URLs and remove them if found.

If the duplicate responses persist even with a new workflow, the issue is likely on Razorpay's end, and we recommend contacting their support team for further investigation.

 

[abhishek@tbn]

I have checked Razorpay all my webhooks are added once only. So can you please suggest to move further. Please find the attached screenshot from Razorpay.

 

[Preeti Paryani]

Here are the troubleshooting steps:

To troubleshoot this, we suggest:

1. Create a new workflow with a fresh webhook URL and test if it captures the response only once.
2. Check your Razorpay dashboard for any duplicate webhook URLs and remove them if found.

If the duplicate responses persist even with a new workflow, the issue is likely on Razorpay's end, and we recommend contacting their support team for further investigation.

 

[abhishek@tbn]

Hello Preeti,

We raised the ticket to Razorpay as well and we got following steps to follow. Steps are mentioned below.
Step 1: Create a Webhook in Pabbly
Open Pabbly Connect.

Click “Create Workflow” → Name it (e.g., “Razorpay Payment Filter”).

Choose Webhook as the trigger.

Copy the webhook URL generated.

Step 2: Set up Webhook in Razorpay
Log in to your Razorpay account.

Go to Settings > Webhooks.

Click “+ Add Webhook”.

Paste the Pabbly webhook URL.

Choose events like payment.captured or order.paid.

Save.

➡ Now make a test payment so Pabbly can capture the webhook response.

Step 3: Lookup in Google Sheets
After Webhook trigger step, click “+” to add an action.

Choose Google Sheets → Action: Lookup Spreadsheet Row.

Connect your Google account.

Choose your spreadsheet and worksheet.

In the "Lookup Column", choose the column where payment_id is stored.

In the "Lookup Value", map the payment_id from the webhook.

Step 4: Add Filter to Prevent Duplicates

Click “+” after Lookup step.

Choose Filter.

Set this condition:

Field: payment_id (from Google Sheet lookup)

Condition: Does Not Exist

If it's a new ID → Flow continues
If it exists already → Flow stops (no duplicates)

And here is our Workflow url where we have implemented all above steps.
Workflow: https://connect.pabbly.com/workflow/sendwebhookdata/IjU3NjYwNTZiMDYzMjA0MzU1MjZlNTUzMzUxMzci_pc
Please guide us what to do next because we are still getting duplicate records.
And one more thing I want to ask is, can it be a reason if our GSheet have morethan 1.5Lac data and still growing everyday?

Please guide here too.

-Abhishek

 

[Preeti Paryani]

Hello @abhishek@tbn,

Thank you for sharing Razorpay's team response and workflow details.

Upon reviewing, everything appears to be functioning correctly on our end. However, to better understand the concern, could you please point out the specific duplicate records you're referring to?

Additionally, we noticed that your workflow includes a Lookup Spreadsheet action, which is processing a significant amount of data. Please note that in such cases, the action may occasionally result in a "Response not received in 25 seconds" error. This happens when the lookup process takes longer than the allowed execution time.

To assist you further, please share the relevant task history where the issue occurred. This will help us investigate more effectively.

Looking forward to your response.

 

[abhishek@tbn]

Hello @preeti,

Sorry for the delayed response.

Please find the attached task history where are getting duplicate entries and this issue is still persist.

I request you to kindly resolve it ASAP.

 

[ArshilAhmad]

Razorpay triggers are based on descriptive webhooks, and we do not have any control over the data sent by the source application to Pabbly Connect. If Razorpay sends the data twice, your workflow will also be triggered twice.

You can test this by connecting your Razorpay account to webhook.site—you will receive the data twice there as well.

Even though the data received may look the same at first glance, there are minor differences between the two payloads.

Task History ID - IjU3NjUwNTY4MDYzNjA0Mzc1MjY4NTUzMzUxM2I1MTZhNTQzMjBmMzki_pc
Task History ID - IjU3NjUwNTY4MDYzNjA0Mzc1MjY4NTUzMzUxM2I1MTZhNTQzMzBmMzki_pc

Razorpay Payload Difference - Diffchecker

Razorpay Payload Difference - { "payload<=-+($@$)+-=>payment<=-+($@$)+-=>entity<=-+($@$)+-=>wallet": null, "payload<=-+($@

www.diffchecker.com

We recommend reaching out to Razorpay's support team to understand why the data is being sent twice from their end. The issue cannot be resolved from our end.

 

[Resham]

We raised the ticket to Razorpay as well and we got following steps to follow

Hello Abhishek,

This is a known issue originating from Razorpay’s end. Since you’ve already raised a ticket with them and received a workaround, could you please share a screenshot of their response for our reference?