Composio - Notice history

The incident has been resolved.

This incident has been resolved.

Backlog of webhook payloads is cleared now.

We have started processing our webhook based triggers and backlog is being cleared now.

There will still be some delay as the backlog gets flushed.

No impact on polling triggers as mentioned above.

This incident has been resolved.

Our latency numbers are looking good and slack triggers continue to work now.

Slack triggers are turned off as part of remediation of platform latencies.

This incident has been resolved. Rate limits have been upgraded.

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.

We've reverted the change and webhook delivery has resumed. We're actively monitoring to confirm full recovery.

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.

This incident has been resolved. It was a regression in the filtering query we use for polling new emails. We have reverted the change and actively monitoring it.

We have identified that the issue is scoped to GMAIL_NEW_GMAIL_MESSAGE trigger and is affecting a very limited set of customers - 2% of GMAIL_NEW_GMAIL_MESSAGE trigger instances.