@devries-cameron20 / composio-1 / commits / beffa6b05
Fork 0

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: update managed polling minimum from 15 to 2 minutes (#5149)

## What changed The docs said managed auth enforces a 15-minute minimum polling interval. That's out of date: the minimum on Composio-managed auth is 2 minutes. This PR updates the claim on 3 pages, one line each: 1. `docs/content/docs/authentication/custom-app-vs-managed-app.mdx`: "You need faster polling triggers" bullet 2. `docs/content/docs/triggers.mdx`: polling latency cell in the Realtime vs polling table 3. `docs/content/docs/setting-up-triggers/troubleshooting.mdx`: Gmail polling wait time The latency and troubleshooting text describe 2 minutes as the shortest allowed interval, not a fixed schedule. A trigger configured with a longer `interval` waits that long. The March 2026 polling changelogs still say 15 minutes. They're dated records, so I left them as they are. ## Checks - `bun run test` in `docs/`: 810 pass, 5 fail. The same 5 `source-backed page freshness` tests fail on `next` without this change, so they're not caused by it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Lingala committed Oct 29, 2026 at 19:33 UTC beffa6b0546f73b1f756e4dec8888fb8e1fd3716
3 files changed +3 -3
docs/content/docs/authentication/custom-app-vs-managed-app.mdx
+1 -1
@@ -26,7 +26,7 @@ Bring your own credentials when any of these apply:
26 - **Your users see OAuth consent screens.** In production, users should see your app name, not "Composio." This is the most common reason to switch.
27 - **You need custom scopes.** Composio's default scopes may not include everything you need (e.g., write access to a specific Google API).
28 - **You're hitting rate limits.** Managed apps share quota across all Composio users. Your own app gets a dedicated quota.
29 -- **You need faster polling triggers.** Managed auth enforces a 15-minute minimum polling interval; your own app can use shorter polling intervals where supported.
29 +- **You need faster polling triggers.** Managed auth enforces a 2-minute minimum polling interval; your own app can use shorter polling intervals where supported.
30 - **You're connecting to a custom instance.** Self-hosted or regional variants (e.g., a private Salesforce subdomain) need their own OAuth app.
31 - **Enterprise customers require your branding end-to-end.**
32
docs/content/docs/setting-up-triggers/troubleshooting.mdx
+1 -1
@@ -38,7 +38,7 @@ With Composio-managed OAuth, Composio manages provider ingress. If matching even
38
39 ## Test Gmail polling with a new message
40
41 -Gmail polling on Composio-managed auth can take up to about 15 minutes. An empty legacy `last_synced_at` field alone does not establish that polling has stopped. Gmail polling uses a mailbox history cursor, and its first successful poll establishes a baseline. Messages that existed before that baseline are not a backfill.
41 +A new message can take up to one full polling interval to appear. That's the `interval` set on the trigger. On Composio-managed auth, the shortest allowed interval is 2 minutes. A trigger with a longer interval waits that long. An empty legacy `last_synced_at` field alone does not establish that polling has stopped. Gmail polling uses a mailbox history cursor, and its first successful poll establishes a baseline. Messages that existed before that baseline are not a backfill.
42
43 Wait for the first successful poll to establish the baseline, then send one new message to the connected mailbox. Keep its Gmail message ID and UTC arrival time, then check the intended trigger instance and your webhook delivery logs after another full polling interval. If you need older messages, fetch them separately with Gmail tools.
44
docs/content/docs/triggers.mdx
+1 -1
@@ -19,7 +19,7 @@ Under the hood, Composio learns about events in one of two ways. You don't confi
19 | Kind | How Composio learns about the event | Latency | Examples |
20 |---|---|---|---|
21 | **Realtime** | The provider pushes the event to Composio the moment it happens. | Near-instant | Slack, Asana, Notion, Outlook |
22 -| **Polling** | Composio checks the provider on a schedule. | Up to ~15 min on Composio-managed auth | Gmail, Google Calendar |
22 +| **Polling** | Composio checks the provider on a schedule. | Up to the trigger's polling interval. On Composio-managed auth, the shortest allowed interval is 2 min | Gmail, Google Calendar |
23
24 Either way, the event lands in the same place: your subscription or webhook URL, in the same payload shape.
25