Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 23:30 UTC
docs(changelog): sharpen polling_failure_in_composio_infra row
'Unhealthy' was vague and circular. Replace with the concrete operational cause (failed to fetch events after repeated retries). Drop the re-enable instructions — users already know a disabled trigger is re-enabled the same way as any other. Drop the 'reliability continues to improve' forward-looking tail; 'Rare in practice' carries the reassurance on its own. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Anshu Garg committed
Apr 23, 2026 at 19:32 UTC
4346b57592ec2dbc3a577c3e49d7f0ea4d199e9a
1 file changed
+1
-1
docs/content/changelog/04-23-26-trigger-disabled-event.mdx
+1
-1
@@ -15,7 +15,7 @@ The event is emitted only for platform-initiated disables. `data.disabled_reason
15
| `connection_expired` | The connected account entered `EXPIRED` and the trigger was paused. Auto-re-enabled when the account returns to `ACTIVE`. |
16
| `subscription_auth_failure` | The provider rejected the credentials when Composio tried to refresh the webhook subscription. Re-auth the connection to resolve. |
17
| `subscription_refresh_failure` | Composio could not reach the provider to refresh the webhook subscription (provider error, timeout, or network issue). Re-enable the trigger once the provider is healthy. |
18
-| `polling_failure_in_composio_infra` | A polling trigger was reported unhealthy by Composio's polling infrastructure. Rare in practice, and the reliability of our polling stack continues to improve. |
18
+| `polling_failure_in_composio_infra` | Composio's polling service failed to fetch events for this trigger after repeated retries. Rare in practice. |
19
20
The event does not fire when you disable a trigger yourself — neither through `PATCH /api/v3/trigger_instances/manage/{id}` nor by deactivating the connected account via `PATCH /api/v3/connected_accounts/{id}/status`.
21