Emails Sent TWICE on "Gmail: Sent Email"

[Taiff1]

Your Task History ID

IjU3NjAwNTZiMDYzZjA0MzY1MjY5NTUzNTUxMzc1MTZiNTQzMSI_3D_pc

Hello,

I'm getting emails sent out TWICE from the "Gmail: Send Email" module?
Could it be because of the "No Of Retry"=2 from the module?

The email send is also at the end of two conditionals:

Would that be the issue to?

 

[Pabblymember11]

Hey @Taiff1

Can you please share the task history ids for both executions through which the two emails have been sent?

IjU3NjAwNTZiMDYzZjA0MzY1MjY5NTUzNTUxMzc1MTZiNTQzMSI_3D_pc

Since this task history Id, it has sent only one email. No more than an email has been sent.

 

[Taiff1]

Sorry... didn't realize. Here are some of the IDs that are generating two emails:

1. IjU3NjAwNTZiMDYzZjA0MzY1MjZlNTUzNjUxMzM1MTZhNTQzMyI_3D_pc
2. IjU3NjAwNTZiMDYzZjA0MzY1MjZkNTUzNTUxMzU1MTY1NTQzMyI_3D_pc
3. IjU3NjAwNTZiMDYzZjA0MzU1MjY0NTUzMDUxMzE1MTZhNTQzMCI_3D_pc
4. IjU3NjAwNTZiMDYzZjA0MzQ1MjZjNTUzZDUxMzM1MTY2NTQzMSI_3D_pc
5. IjU3NjAwNTZiMDYzZTA0MzM1MjZiNTUzMzUxMzA1MTYyNTQzOSI_3D_pc
6. IjU3NjAwNTZiMDYzZTA0MzM1MjZhNTUzMTUxMzU1MTZhNTQzMCI_3D_pc
7. IjU3NjAwNTZiMDYzZTA0MzI1MjY4NTUzNDUxMzU1MTY2NTQzOCI_3D_pc

 

[Pabblymember11]

Hey @Taiff1

As we can see from your shared task history, you are getting different data comments from the "LoopedIn" and since the same user had created several different comments or the LoopedIn has sent the same webhook response twice or you might have configured the same webhook URL twice.

 

[Taiff1]

Why does "No Of Retry" show 2?

 

[Pabblymember11]

Why does "No Of Retry" show 2?

Since the API response you are getting is coming from Gmail and if you're experiencing issues with Gmail or have specific questions about its behavior, it's best to consult the official Gmail Help Center or reach out to Google support for the most accurate and up-to-date information.

 

[Taiff1]

You said earlier that LoopedIn had called the webhook twice. Where can I see that?

 

[Pabblymember11]

Hey @Taiff1

You may need to contact the LoopedIn team itself to verify the same.

 

[Taiff1]

The LoopedIn trigger was created by you guys, right?

 

[Pabblymember11]

The LoopedIn trigger was created by you guys, right?

Kindly check the same from the LoopedIn application, since it is a webhook-based trigger event "Webhook By Pabbly" trigger event which only captures the webhook response once send by the application.

You can check it through a webbooks testing site called webhook.site.

You can copy the webhook URL provided by Webhook.site inside LoopedIn and do the test event inside Jira to see if the webhook is being come twice or not inside Webhook.site. This will double-confirm the issue.

Here is a sample video that you can follow to track the webhook issue: