CRM Rate Limits

What this means

Every CRM platform limits how many API requests an app can make in a given window — so no single integration can overload the system. Playwise HQ respects these limits by design: it paces its requests, and when your CRM signals that the limit is near or reached, Playwise slows down and retries automatically.

A rate limit exceeded warning — most often seen during a backfill, which reads many records quickly — means exactly that: the job hit your CRM’s ceiling, backed off, and will continue at a gentler pace.

The key reassurance

A rate-limit warning is a temporary slowdown, not data loss.

• Nothing is skipped — requests wait and are retried once the CRM allows them.
• Backfill jobs finish on their own; they just take longer.
• Incoming webhook events are unaffected on the CRM side and continue to queue and process normally.

There is no action required. The warning exists so you know why things are moving slower than usual.

Why it happens

• A backfill over a large CRM dataset — the most common trigger.
• Other apps connected to your CRM sharing the same limit, leaving Playwise less headroom.
• A lower CRM plan tier with tighter API allowances.

If it happens constantly

Occasional warnings during a backfill are entirely normal. If you see them persistently during day-to-day sync:

1. Check whether other integrations in your CRM are unusually busy.
2. Avoid launching backfills during your team’s peak CRM hours.
3. Check whether your CRM plan tier offers higher API limits.

Still stuck?

If sync feels permanently slow and rate-limit warnings never stop, see the troubleshooting guide or contact support — persistent limiting outside of backfills is worth investigating together.