Composio - Notice history

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.

Hosted web search requests failed due to a capacity limit with the upstream search provider. Capacity has been restored and we have verified full recovery. No action is needed on your end.

This incident has been resolved. Tool executions across the impacted toolkits across all versions are now working normally.

We've narrowed down the impact to only the following toolkits and only versions strictly before 20260618_00 . Impacted toolkits: COMPOSIO_SEARCH YELP INSTACART TAVILY GEMINI SEAT_GEEK BROWSER_TOOL SERPAPI . Customers using version=latest remain unaffected.

The root cause has been identified and the fix is rolling out.

This incident has been resolved. Auth refresh for Linear was being rate limited by Linear, it was resolved after increasing the refresh window. End users who have multiple (more than 3-4) Linear Accounts connected with their agents may still see auth refresh failures.

We have temporarily eased its restrictions. The Cloudflare WAF remains in place. If you receive a 403 with a request id resembling something like "cle:..." or some other 3 letter region prefix please try again or reach out to us.
This incident has been resolved.

This incident has been resolved.

CLI auth was broken and all existing CLI auth was revoked hence functionally bricking CLI