https://linen.dev logo
Powered by
Gmail Triggers not working
# 🖥│support-forum
a
@Uday We are not receiving triggers for some users in our platform. A few weeks ago we had an issue with gmail accounts expiring, this is urgent to us. Thanks
I'm seeing a lot of triggers that were created again
is this an automated internal process ?
u
Hey @AlvaroVargas11, No, ideally, we don’t automatically create triggers on users’ behalf. Could you share a few trigger IDs that you’re facing issues with? It'll help us debug the issue.
a
ti_uE5sNV63EUsm
@Uday
i created this one today and it stopped working
stopped working at around 4:30 pm gmt-3
u
"*stopped working at around 4:30 pm gmt-3*" — Could you share a few logIDs before the trigger stopped working? It'll help us in debugging.
a
log_OwIY0q7ttYbi
this is the last one before it stopped working
the weird thing is that the webhooks that I didn't receive in that gap, I received them later .. as if they got stuck, and then unstuck all of a sudden
u
@AlvaroVargas11, yes, I can see a few logIDs on Feb14. Also, "*stuck, and then unstuck*"— I just checked your connected account and your refresh is working as expected, this happens when you disable your connected account(
INACTIVE
) and then re-enabling it.
a
@Uday that's weird i didn't do anything from my end. My account was connected since October 2025 (this is my prod account). We had to re-create the triggers on friday because something broke, but we didn't do anything from our end...
u
@AlvaroVargas11, I just checked your triggerId and looks like it was created around Dec 5th. "*i created this one today and it stopped working*" — You might've tried to create a new trigger for the same connected account with the same trigger config, which will just update the existing trigger instead of creating a new one.
a
@Uday this happened again to 2 users yesterday. This issue, and triggers/oAuth randomly expiring is killing us in prod. Our app stops working https://cdn.discordapp.com/attachments/1471883243136483368/1476865207233024020/image_199.png?ex=69a2ad68&is=69a15be8&hm=048bf4ffad0ac3d5be7b2a1d2051473a4b49e7746378603ddada2043f2837dfe&
as you can see in the image, this user stopped receiving events from composio for 5 hours - then received them all at once
u
@AlvaroVargas11, could you share the log IDs of a few trigger logs? It'll help us in debugging.
a
@Uday the UI is breaking when trying to filter by trigger id, so I can't get log ID's. https://www.loom.com/share/09b673994f3346a181a887df48420333 In the image I'm showing the trigger ID, Date timestamp, connection ID. Your team can easily query the logs with that. The number of errors, and the amount of work we need to do to help composio fix them, is becoming increasingly frustrating
u
2 Views
PreviousNext
Powered by