Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs: polling interval grace period for existing customers
- Add changelog for March 13 grace period announcement - Update old changelog with grace period notice - Update triggers.mdx, troubleshooting, custom-app docs - New triggers: 15-min minimum now - Existing triggers: Grace period until May 1, 2026 - Solution: Use your own OAuth app Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Palash Kala committed
Mar 13, 2026 at 18:48 UTC
1f6a5b448ebceebe2e5c5dad6fd81c50c3ab90b1
6 files changed
+45
-4
docs/content/changelog/03-11-26-polling-interval-changes.mdx
+4
@@ -4,6 +4,10 @@ description: "Default polling interval increasing from 1 minute to 15 minutes, w
4
date: "2026-03-11"
5
---
6
7
+<Callout type="warn">
8
+**Update (March 13, 2026):** Existing customers have a grace period until May 1, 2026. See [updated changelog](/docs/changelog/2026/03/13).
9
+</Callout>
10
+
11
We're updating **polling trigger intervals** to improve platform reliability and avoid rate limiting. This change affects how frequently polling triggers execute.
12
13
## What's Changing?
docs/content/changelog/03-13-26-polling-interval-grace-period.mdx
new
+37
@@ -0,0 +1,37 @@
1
+---
2
+title: "Polling Intervals: Grace Period for Existing Customers"
3
+description: "Existing customers keep 1-minute polling until May 1. New triggers default to 15 minutes."
4
+date: "2026-03-13"
5
+---
6
+
7
+We're introducing a **grace period** for existing customers to transition to the new polling interval limits.
8
+
9
+## Timeline
10
+
11
+| Customer Type | Polling Interval | Until When |
12
+|---------------|------------------|------------|
13
+| **Existing** (triggers before today) | 1 minute | May 1, 2026 |
14
+| **New** (triggers from today) | 15 minutes minimum | Now |
15
+
16
+If any of your triggers were affected by the recent changes, we've restored them to their original intervals.
17
+
18
+## Why 15 Minutes?
19
+
20
+Composio-managed OAuth apps share rate limits across all users. At scale, 1-minute polling causes rate limiting and service degradation. The 15-minute minimum ensures reliability for everyone.
21
+
22
+## How to Keep 1-Minute Polling
23
+
24
+Set up **your own OAuth app**. With custom auth:
25
+- Intervals as low as 1 minute
26
+- Your own rate limits
27
+- No platform limits, ever
28
+
29
+<Callout type="warn">
30
+OAuth approval from Google, Microsoft, etc. takes **days to weeks**. Start now.
31
+</Callout>
32
+
33
+→ [Set up your own OAuth app](/docs/custom-app-vs-managed-app)
34
+
35
+## Alternatives
36
+
37
+For real-time events, use **webhook triggers** — instant delivery, no polling limits.
docs/content/docs/custom-app-vs-managed-app.mdx
+1
-1
@@ -24,7 +24,7 @@ Bring your own credentials when any of these apply:
24
- **Your users see OAuth consent screens.** In production, users should see your app name, not "Composio." This is the most common reason to switch.
25
- **You need custom scopes.** Composio's default scopes may not include everything you need (e.g., write access to a specific Google API).
26
- **You're hitting rate limits.** Managed apps share quota across all Composio users. Your own app gets a dedicated quota.
27
-- **You need faster polling triggers.** Managed auth enforces a 15-minute minimum polling interval; your own app can use shorter polling intervals where supported.
27
+- **You need faster polling triggers.** New triggers with managed auth have a 15-minute minimum (existing triggers until May 1, 2026). Your own OAuth app can use intervals as low as 1 minute — now and always.
28
- **You're connecting to a custom instance.** Self-hosted or regional variants (e.g., a private Salesforce subdomain) need their own OAuth app.
29
- **Enterprise customers require your branding end-to-end.**
30
docs/content/docs/triggers.mdx
+1
-1
@@ -11,7 +11,7 @@ When events occur in apps, like a new Slack message, a GitHub commit, or an inco
11
There are two delivery types:
12
13
- **Webhook triggers**: Apps like GitHub and Slack push events to Composio in real time. When an event fires, Composio forwards the payload to your webhook endpoint.
14
-- **Polling triggers**: For apps that don't support outgoing webhooks (e.g., Gmail), Composio polls for new data on a schedule. For Composio managed auth, polling intervals have a minimum of 15 minutes. Expect delays between the source event and delivery.
14
+- **Polling triggers**: For apps that don't support outgoing webhooks (e.g., Gmail), Composio polls for new data on a schedule. New triggers with Composio-managed auth have a 15-minute minimum interval; existing triggers (before March 13, 2026) keep current intervals until May 1, 2026. [Use your own OAuth app](/docs/custom-app-vs-managed-app) for shorter intervals.
15
16
## Working with triggers
17
docs/content/docs/troubleshooting/triggers.mdx
+1
-1
@@ -9,7 +9,7 @@ Check the error message — the connected account might not have sufficient perm
9
10
## Not receiving payloads
11
12
-- **Polling triggers** (e.g., Gmail): These check for new events on an interval you configure. For Composio managed auth, intervals below 15 minutes are not supported.
12
+- **Polling triggers** (e.g., Gmail): These check for new events on an interval you configure. New triggers with Composio-managed auth have a 15-minute minimum. Existing triggers keep current intervals until May 1, 2026. [Use your own OAuth app](/docs/custom-app-vs-managed-app) for shorter intervals.
13
- **Webhook URL**: Ensure your URL is publicly accessible and returns a `2xx` status code.
14
- **Trigger status**: Verify the trigger is enabled, not disabled.
15
- **Logs**: Check the [trigger logs](https://platform.composio.dev?next_page=/logs/triggers) in the dashboard for delivery attempts and errors.
docs/content/docs/using-custom-auth-configuration.mdx
+1
-1
@@ -9,7 +9,7 @@ You create a custom auth config when you need to provide your own credentials fo
9
- **Toolkit has no managed auth**: PostHog, Tavily, Perplexity, etc. require your own credentials
10
- **White-labeling**: Show your app name on OAuth consent screens instead of "Composio". See [White-labeling authentication](/docs/white-labeling-authentication)
11
- **Rate limits**: Composio's default OAuth app shares quota across all users. Your own app gets a dedicated quota
12
-- **Faster polling triggers**: Composio managed auth enforces a 15-minute minimum polling interval. Your own OAuth app can use shorter polling intervals where supported
12
+- **Faster polling triggers**: New triggers with Composio-managed auth have a 15-minute minimum. Your own OAuth app can use intervals as low as 1 minute
13
- **Custom scopes**: You need permissions beyond what Composio's default app has approved
14
- **Custom instance**: Connecting to a self-hosted or regional variant (e.g., custom Salesforce subdomain)
15