Composio - Notice history

This incident has been resolved. We're seeing full recovery on delivery volumes.

We have implemented the configuration fix and monitoring

We've identified the root cause as a fall out of our mitigation towards the ongoing security incident. We had rotated internal secrets across multiple internal services but due to a misconfiguration in the delivery service, the inter-service communication between the trigger & delivery service is severed. We are working on restoring this ASAP.

Between 10:17 and 10:23 AM PT, a subset of new connection account creations returned errors. The issue has been fixed and traffic is back to normal. Existing connections and tool execution were unaffected.

Between 2:15 and 2:38 PM PT, a subset of tool execution requests returned errors. The issue has been fixed and traffic is back to normal.

Webhook triggers are disabled

We are still investigating the fix. We will post an update in a couple of hours.

Between 10:49 and 11:16 AM PT, new connection account creations saw elevated errors and Slack webhook trigger deliveries were delayed. The issue has been fixed and traffic is back to normal. Existing connections continued to work throughout

Between 12:14 and 12:21 PM PT, a subset of tool execution requests saw elevated latency. The issue has been fixed and traffic is back to normal

We have identified the root cause and are continuing to work on a fix for this incident.

Webhook triggers are also resolved now and subscribers should be receiving the payloads.

Old Polling are also back.
We are trying to get back webhook triggers as well.

New polling triggers are fine. Older triggers - We are getting them back up

Triggers are still under investigation

We found the cause, now fixing

This incident has been resolved.

We've implemented a fix and monitoring the current status. All components are operational at the moment.

We are continuing to work on a fix for this incident. Triggers isn't working. Rest of the components work as expected.

We've addressed the failures in platform and API. We've tentatively disabled polling triggers.