Issues with Gmail triggers

What to do

• Check whether you use Composio Triggers V2, Triggers V1. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-07-02 04:48 UTC and 2026-07-02 04:48 UTC may need a replay.

• Subscribe to Composio's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=composio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Composio 1

1. resolvedJul 2, 2026, 4:48 AM UTC

   Type: Incident Duration: 13 hours and 7 minutes Affected Components: Triggers V2, Triggers V1 Jul 2, 17:55:00 GMT+0 - Resolved - This incident has been resolved. Root cause: a change we had already reverted was re-introduced by an automated sync, re-causing yesterday's regression in the new-email polling logic. We're adding checks to prevent recurrence, and we're sorry for the disruption. Jul 2, 17:52:00 GMT+0 - Monitoring - We've reverted the change and webhook delivery has resumed. We're actively monitoring to confirm full recovery. Jul 2, 17:40:00 GMT+0 - Identified - We've identified the cause. A fix we reverted yesterday was unintentionally re-applied to production during a routine code sync, which re-introduced the same regression in our new-email polling filter. Impact is limited to GMAIL\_NEW\_GMAIL\_MESSAGE triggers configured without an explicit Gmail label. Less than 2% of overall GMAIL\_NEW\_GMAIL\_MESSAGE triggers are affected. We are rolling back the change now. Jul 2, 04:48:00 GMT+0 - Investigating - We're investigating reports that the GMAIL\_NEW\_GMAIL\_MESSAGE trigger has stopped delivering webhooks for a subset of accounts.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.