Gmail Integration Service triggers twice (on non-existent condition)

[AndyMenon]

I’m not sure what changed but the Gmail Integration Service trigger that was working correctly has started to trigger automations twice. And I am not sure if I’m missing anything because for nearly a month, this setup was working without issues.

Here is how it is happening:

Gmail IS Trigger is set to trigger on a specific subject line trigger and from only certain senders.

This works correctly the first time around when an email fitting the above signature is sent to the target gmail email inbox.

The Unattended Automation is kicked off by the trigger.

The automation reads the email (with Mark as read option set to true).

The automation performs the business function and then prepares a suitable response with an entirely different subject line!

Automation responds to the original email by using the Email Item ID of the original email

Email with an entirely new subject line arrives in the email inbox

Automation deletes the original email soon after responding.

The job ends without incident.

TO NOTE: By this time the original email has been deleted and does not exist in the Inbox

ISSUE:

As soon as the response to the original email is received, the job is triggered a second time!

If I check the running logs, the job has miraculously read the content of an email that no longer exists!

How is this possible?

The Integration trigger is supposed to trigger on a specific subject line signature. How is that it is triggering based on an entirely different subject line?

This issue started yesterday, March 6 2026.

I have updated all the packages and redeployed the automation, but to no avail!

Package stack:

Studio Version:

[Sanjay_Bhat]

Hi @AndyMenon

I had faced the same issue in outlook event trigger

Fix : Keep 1 more trigger condition for the folder. For Ex: Keep trigger condition saying when the mail is recieved to Inbox/MailFolder only trigger

Hope this helps!

[AndyMenon]

Hi Sanjay

My IS trigger points to Inbox already.

I tried several fixes but none of them worked. There is no reason why the IS trigger would kick of a second run of the automation when the first job run is still in flight AND no Email Received Event has occurred in the inbox AND when there are no unread messages in the inbox.

From the Orchestrator log of the automation, I can see that the IS trigger is picking up the email with the same internal Email ID value twice. Why would it do that when that Email ID is not part of the Email Received Event anymore?

It worked for almost 3 weeks with no issues. I don’t know why these mechanisms have become so unreliable and can’t remain stable.

Andy Menon

Founder, Lead Solution Architect & Engineer | UiPath MVP 2021-25,

www.rpavanguard.com | admin@rpavanguard.com

[AndyMenon]

Hi @Sanjay_Bhat ,

Are you using the email as merely a trigger or are you reading the new email? If yes, what is the first activity you are using in your automation to read the triggered email message?

Thanks,
Andy

[Sanjay_Bhat]

@AndyMenon

Yes I am reading the mail as well,

Email Trigger via Integration Service --> How can the process read the email?

Hello there, I’m studying the possibility to trigger a process when email is received. I’ve come upon the Integration Service and I’ve created a connection and a trigger when an email is received. Now comes the question here: Is there any way to get the trigger email Subject and Body (for instance)? As far as I see, the trigger pass some string type arguments to the process but none of them contain any information about the email Input Values: Object UiPathEventConnector: uipath-google-gmail…

Create an argument UiPathEventObjectId and pass it as email Id and basically it reads the mail which triggered the process

Hope this helps!

[AndyMenon]

Yes! That was the way I used to do it. Add those 4 arguments as inputs to the automation. But here’s the situation on my end as of today.

Therefore, I could not create a Disconnected trigger. So, I did it differently.

Added an Email Received Trigger in the automation to read the email
Deployed the automation by creating a Connected Trigger Event in the Orchestrator

Here is what I see:

The retriggering occurs when I use the Reply to Email activity to reply back to the original Gmail Item. This is happening even when I change the subject line to a completely different string! Or, even if I mark the email as read when I retrieve it!

But the retriggering stopped when I did the following:

• Delete the original email (permanent delete is false)
• Used the Send Email activity to send an entirely new email back to the sender of the original email .

I have performed 2 tests since this change and the retriggering has stopped. Here is the list of job result status.

1. The retriggers are in Red that I had to stop.
2. After the change, 2 consecutive tests ran successfully without a faulty retrigger.

What’s the issue with the Connected Trigger setup?

Unless I’m missing something, this is what I see:

• The filters on the trigger need to be added inside the process in the Email Received activity - if those conditions change tomorrow, we have to redeploy the application with updates to these tightly coupled conditions.
• If it does not find the email with the conditions specified in the filter, the Email Received activity throws an exception and causes the process to be retriggered at least a couple of times.