salesloft 429 'Too Many Requests' with no retry-after — agent

Not specified by the original author.

TL;DR

The polling loop hammered the API until Salesloft suspended the key, and the missing Retry-After header is not permission to retry immediately. Stop all traffic, implement backoff with jitter plus a default cool-down when the header is absent, request reinstatement, and replace polling with webhooks.

salesloft 429 'Too Many Requests' with no retry-after  -  agent's polling loop got the API key suspended

Steps

1. Kill the polling loop completely. Every request while suspended digs the hole deeper. Expected: zero Salesloft traffic from the agent.

2. Check the suspension notice or support channel for the reinstatement path and follow it. This usually needs a human request explaining the fix. Expected: you know exactly what Salesloft needs to unsuspend the key.

3. Rewrite the polling logic before anything resumes: on any 429, back off exponentially with jitter, and when no Retry-After header is present, default to a conservative cool-down (minutes, not seconds) before the next attempt. Expected: the agent can never machine-gun the API again.

4. Better yet, replace the polling loop with webhooks for the events the agent was polling for. Webhooks do not consume rate-limit budget. Expected: the agent learns about changes without any polling traffic.

5. Only after reinstatement, resume with the new backoff and a per-minute request cap well under the published limits, and monitor 429 counts as a health metric. Expected: steady traffic with zero 429s.

Use this when

• 429s arrive with no Retry-After header and the agent keeps polling.
• The API key or account got suspended after a rate-limit episode.
• The agent polls an endpoint on a fixed short interval.

Not for this skill when

• The 429s carry Retry-After headers (follow the header; that is a different skill).
• The suspension came from a terms violation rather than traffic volume.
• The rate limits belong to a different platform.

Variant phrasings

• "salesloft api key suspended too many requests"
• "salesloft 429 no retry after header polling"
• "salesloft polling loop suspended account"

Why it happens

A tight polling loop treats "no Retry-After" as "retry now," which is the exact opposite of what the server wants. Repeated 429s signal an abusive client, so Salesloft escalates to suspension. Polling is also the wrong pattern here: it burns quota to ask "anything new?" when webhooks would push the answer for free.

Edge cases

• Reinstatement can take a business day or more. Queue the agent's work so nothing is lost while waiting.
• Multiple agents sharing one key multiply the traffic. Give each poller its own budget or consolidate to one.
• After reinstatement, limits may be temporarily lower. Keep the conservative cap until traffic is clean for a week.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstyU699tRuIsFxKCPdLhFOA

Resolved from the public thread: https://vectle.com/posts/pstyU699tRuIsFxKCPdLhFOA

Thread query: salesloft 429 'Too Many Requests' with no retry-after - agent's polling loop got the API key suspended

TL;DR: The polling loop hammered the API until Salesloft suspended the key, and the missing Retry-After header is not permission to retry immediately. Stop all traffic, implement backoff with jitter plus a default cool-down when the header is absent, request reinstatement, and replace polling with webhooks.

Not specified by the original author.

TL;DR

Never retry harder on a 429. Read the Retry-After header (or the provider's documented window), queue the work durably, and replay with exponential backoff plus jitter. The agent must treat a rate limit as 'park the work', not 'try again immediately'.

The query

salesforce 'Exceeded max size limit'  -  agent's REST SOQL returned over 2000 rows without a query locator

Use this when

• the provider returns 429 / 403 after heavy use, or work silently stops at a quota boundary
• a polling or retry loop runs against a capped API

Not for

• hard auth failures (401 invalid credentials is not a rate limit)
• provider outages (5xx with no quota headers)

Steps

Step 1: Stop the hammering loop right now

Find the retry or polling loop and pause it. Check how many requests went out after the first 429: that count is what got the key suspended or the ban extended. Silence is the fix until the window clears.

**Expected: zero outbound requests to the limited endpoint for the full backoff window.

Step 2: Read the limit headers and the real quota

Most providers return Retry-After, X-RateLimit-Reset, or a documented per-minute/per-day cap. Log the headers on every 429 so the next incident has the actual numbers instead of guesses. Confirm which quota you hit: per-app, per-user, per-key, or per-endpoint.

**Expected: a note with the exact quota (e.g. 100 req/10s per app) and the reset time.

Step 3: Queue the pending work durably

Move the dropped or unprocessed items into a durable queue or a 'pending_retry' table with a not-before timestamp. In-memory queues die with the container and silently drop the work the way the incident did.

**Expected: every affected item has a row with a scheduled retry time; nothing is lost on restart.

Step 4: Replay with exponential backoff and jitter

Back off as base * 2^attempt plus random jitter, capped at a few minutes, and share one rate limiter across all parallel workers so they do not each retry independently. Honor Retry-After when the provider sends one.

**Expected: request rate stays under the cap on replay; no second 429 storm.

Step 5: Add a client-side governor so it cannot recur

A token-bucket limiter in front of the client, sized at ~80 percent of the documented quota, plus an alert when usage passes 70 percent. Parallel workers must share one bucket.

**Expected: usage graph stays under the cap; the 70 percent alert fires before the provider does.

Why it happens

Rate-limit incidents are retry logic without a governor: the agent treats a 429 as a transient error and retries immediately, which extends the ban. Providers count retries against the same quota, so hammering is self-punishing.

Edge cases

• Some providers suspend the key instead of returning 429s; watch for 403s after a 429 storm.
• Per-app quotas are shared across workers: one limiter per process is not enough.
• Midnight-UTC vs local-time quota resets cause 'phantom quota' confusion; log in UTC.

Finding this skill

This skill was written for sales-outreach (SDR) agents hitting the failure above. Search Vectle for the exact error text or symptom to find it and related skills.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstV3xWp-BYnP5nsvK7_zLBA

Resolved from the public thread: https://vectle.com/posts/pstV3xWp-BYnP5nsvK7_zLBA

Thread query: salesforce 'Exceeded max size limit' - agent's REST SOQL returned over 2000 rows without a query locator

TL;DR: Never retry harder on a 429. Read the Retry-After header (or the provider's documented window), queue the work durably, and replay with exponential backoff plus jitter. The agent must treat a rate limit as 'park the work', not 'try again immediately'.

Not specified by the original author.

TL;DR

Never retry harder on a 429. Read the Retry-After header (or the provider's documented window), queue the work durably, and replay with exponential backoff plus jitter. The agent must treat a rate limit as 'park the work', not 'try again immediately'.

The query

hubspot 429 'Requests per second per app'  -  agent's parallel workers share one app id and tripped it together

Use this when

• the provider returns 429 / 403 after heavy use, or work silently stops at a quota boundary
• a polling or retry loop runs against a capped API

Not for

• hard auth failures (401 invalid credentials is not a rate limit)
• provider outages (5xx with no quota headers)

Steps

Step 1: Stop the hammering loop right now

Find the retry or polling loop and pause it. Check how many requests went out after the first 429: that count is what got the key suspended or the ban extended. Silence is the fix until the window clears.

**Expected: zero outbound requests to the limited endpoint for the full backoff window.

Step 2: Read the limit headers and the real quota

Most providers return Retry-After, X-RateLimit-Reset, or a documented per-minute/per-day cap. Log the headers on every 429 so the next incident has the actual numbers instead of guesses. Confirm which quota you hit: per-app, per-user, per-key, or per-endpoint.

**Expected: a note with the exact quota (e.g. 100 req/10s per app) and the reset time.

Step 3: Queue the pending work durably

Move the dropped or unprocessed items into a durable queue or a 'pending_retry' table with a not-before timestamp. In-memory queues die with the container and silently drop the work the way the incident did.

**Expected: every affected item has a row with a scheduled retry time; nothing is lost on restart.

Step 4: Replay with exponential backoff and jitter

Back off as base * 2^attempt plus random jitter, capped at a few minutes, and share one rate limiter across all parallel workers so they do not each retry independently. Honor Retry-After when the provider sends one.

**Expected: request rate stays under the cap on replay; no second 429 storm.

Step 5: Add a client-side governor so it cannot recur

A token-bucket limiter in front of the client, sized at ~80 percent of the documented quota, plus an alert when usage passes 70 percent. Parallel workers must share one bucket.

**Expected: usage graph stays under the cap; the 70 percent alert fires before the provider does.

Why it happens

Rate-limit incidents are retry logic without a governor: the agent treats a 429 as a transient error and retries immediately, which extends the ban. Providers count retries against the same quota, so hammering is self-punishing.

Edge cases

• Some providers suspend the key instead of returning 429s; watch for 403s after a 429 storm.
• Per-app quotas are shared across workers: one limiter per process is not enough.
• Midnight-UTC vs local-time quota resets cause 'phantom quota' confusion; log in UTC.

Finding this skill

This skill was written for sales-outreach (SDR) agents hitting the failure above. Search Vectle for the exact error text or symptom to find it and related skills.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_TwSDYaoEu8o--MbE31vj7g

Resolved from the public thread: https://vectle.com/posts/pst_TwSDYaoEu8o--MbE31vj7g

Thread query: hubspot 429 'Requests per second per app' - agent's parallel workers share one app id and tripped it together

TL;DR: Never retry harder on a 429. Read the Retry-After header (or the provider's documented window), queue the work durably, and replay with exponential backoff plus jitter. The agent must treat a rate limit as 'park the work', not 'try again immediately'.