Skip to main content

Rate limits and scheduling

Common questions about Coalesce API rate limits, HTTP 429 errors, and scheduling the Atlan crawler around your Coalesce job windows.

Does Coalesce enforce API rate limits?​

Yes. Coalesce enforces per-account API rate limits. For most workspaces (a few hundred nodes), the Atlan connector stays well under the threshold and no coordination is needed. For larger workspaces, confirm your rate-limit ceiling with your Coalesce account team before the first crawl.

Workspace sizeRecommended action
Up to ~500 nodesNo coordination required.
500–2,000 nodesConfirm your current rate-limit threshold with your Coalesce account team before the first crawl.
More than ~2,000 nodesThe connector has been validated up to ~2,000 nodes. Contact your Atlan customer success manager before connecting.

Why does each Atlan crawl make many Coalesce API calls?​

For every environment in scope, the connector lists recent runs and then fetches per-node results for each walked run. The total number of API calls scales with the number of environments and runs in the lookback window. Run the connector only as frequently as you need refreshed status—less-frequent crawls are the safer default for large workspaces.

How does Atlan handle HTTP 429 rate limit errors?​

Atlan retries with exponential backoff. The crawl completes but runs slower. If 429 errors are frequent, contact your Coalesce account team to confirm your current threshold and request an uplift if your workspace size justifies it.

When do I schedule Atlan crawls?​

Schedule the Atlan crawl to run after your Coalesce job windows complete. The connector reads from completed runs only—if it fires while a job is still in progress, that run is skipped and the previous completed run's status is used until the next crawl.

Examples:

  • Coalesce runs daily at 02:00 UTC → schedule Atlan at 02:30 UTC or later.
  • Coalesce runs hourly on the hour → schedule Atlan at 15 minutes past the hour or later. The right offset grows with the number of nodes—larger environments need more time and may not suit an hourly cadence. Check with Atlan support before scheduling frequent crawls.
  • Coalesce runs on an irregular cadence → schedule Atlan at a fixed time outside your typical Coalesce job windows, or trigger it via webhook after your Coalesce schedule completes.

What happens if Atlan crawls while Coalesce jobs are running?​

The in-progress run is skipped. The connector uses the previous completed run's status for all affected nodes until the next Atlan crawl after the job finishes. This isn't an error—it's a timing consideration.

See also​

Need help​

If you can't find the answer you're looking for, raise a support ticket.