https://linen.dev logo
Powered by
GMAIL_NEW_GMAIL_MESSAGE Trigger
# 🖥│support-forum
o
When the GMAIL_NEW_GMAIL_MESSAGE trigger is defined with the Query param, It is being triggered also on new draft emails, instead of only on a new emails. This behavious is happenning only when the Query param is configured. And it causing me infinite loop - since the user get an email that contains some search text -> draft a reply -> then the trigger is fired again...
u
Hey @Or, could you share a screen-recording of the complete flow? It'll help our team to reproduce the issue.
o
it's inner implementation of my app, so I don't think the record will help. However I can describe + screenshots: I define the trigger attached in the screenshot - with Query = 'ETA'. which means that it fires if the user recieve an email contains the word 'ETA'. Then my inner implementation, draft a reply for this email. And after the reply drafterd - The trigger fires again, because the draft email also contains the word 'ETA'. you can see example in the screenshot attached of a trigger being fired in a row - it runs infinitely, until I disable the trigger manually https://cdn.discordapp.com/attachments/1475809964324032605/1475894486927278271/image.png?ex=699f255a&is=699dd3da&hm=da3e580e8d1b9391731a17165a1f729e522d69212c5c3fbfc8f3d2a874c63757& https://cdn.discordapp.com/attachments/1475809964324032605/1475894487283929211/image.png?ex=699f255a&is=699dd3da&hm=38d936e559c5f8403d041018497e89bcb59abe3675b9e84c98cf6db57e623429&
u
Hey @Or, thanks for the info. We were able to reproduce the issue and team is investigating the issue.
Hey @Or, we've fixed the issue! Could you try and lmk if issue persists?
o
@Uday It worked perfectly, Thanks!!
Hi @Uday the bug has returned. The trigger GMAIL_NEW_GMAIL_MESSAGE is being triggered when I draft/send message, instead of only when recieving a message...
@Uday kind reminder
a
hey, can you please share the trigger log IDs?
o
log_Yixf5u7FZ9Z0 log_I9PmFgHPK8UT The "log_Yixf5u7FZ9Z0" is fine - after user got a new message. But the "log_I9PmFgHPK8UT" got triggered because of a new draft or a new reply - not because of a new coming email
a
thanks for sharing, let me look into it and circle back.
o
thanks!
@Abhishek any update?
c
We have a similar issue @Abhishek
a
@Or @Cashed sorry for the delay in getting back, I've raised this internally & we'll be working on a fix. I'll circle back with an ETA
o
Hi @Abhishek Kind reminder
a
@Or we've the fix ready and in QA, anticipating it to go live early next week. Please allow me until EOW to get back with a concrete ETA
o
Thanks!
Hi @Abhishek Kind reminder
a
@Or the fix is live! And will apply to existing triggers too
@Cashed ^
@Or @Cashed Wanted to share an update - there was a regression that affected a few percent of triggers due to this change, hence it was reverted. We're working on fixing the issue and will take it live next week. I'll share updates here once I learn more from the team - https://status.composio.dev/cmr2cf3ub00em0lqox5c6l96x Apologies for this.
c
Oh darn okay thanks for the visibility @Abhishek
PreviousNext
Powered by