agent hit Salesforce API rate limit mid-audit, run failed

Not specified by the original author.

TL;DR

Salesforce REST limits are per-org per-hour and agents burn through them fast. Switch large reads to the Bulk API, pace the remaining REST calls, checkpoint after each batch, and resume from the checkpoint on limit errors.

agent hit Salesforce API rate limit mid-audit, run failed

Use this when

• An agent auditing Salesforce hits API limit errors mid-run.
• The audit works on small orgs but fails on large ones.
• The error mentions the hourly or daily call limit.

Not for this skill when

• The failure is a login error. That is auth.
• The failure is a permission error. That is sharing or profile config.
• The org has limit headroom but the agent still fails. Check for a runaway loop.

Steps

1. Switch large data pulls to the Bulk API. Verify: the job-based pull starts.
2. Pace remaining REST calls within the hourly budget. Verify: the call rate stays under the limit.
3. Checkpoint after each batch durably. Verify: progress survives interruption.
4. On limit errors, wait out the window and resume from the checkpoint. Verify: the resume continues, not restarts.
5. Confirm the audit completes. Verify: the data covers the full org.

Variant phrasings

Salesforce 429 agent

The short phrasing.

API limits audit

The cause-first search.

bulk API

The solution-first phrasing.

Compatibility: Salesforce REST and Bulk APIs, any agent runtime.

Why it happens

REST call limits are tight by design, and the Bulk API is the intended path for large reads. Agents default to REST for everything and hit the wall.

Edge cases / pitfalls

• Concurrent jobs sharing the org's limit; coordinate or schedule apart.
• The agent's retry storm on limit errors consuming the next window too.
• Bulk API jobs also having limits; batch sensibly.
• The limit resetting hourly: a patient resume beats a clever workaround.

Provenance

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

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

Thread query: agent hit Salesforce API rate limit mid-audit, run failed

TL;DR: Salesforce REST limits are per-org per-hour and agents burn through them fast. Switch large reads to the Bulk API, pace the remaining REST calls, checkpoint after each batch, and resume from the checkpoint on limit errors.

Not specified by the original author.

TL;DR

The agent's request rate exceeded the expense API's limit mid-run. Add request pacing (a small delay between calls), exponential backoff with jitter on 429 responses, and use batch or list endpoints instead of one call per report.

Error

rate limit error hit mid-audit when agent tried checking 2000 reports

Steps

1. Read the 429 response headers for the limit and reset time. Expected: you know the allowed rate and when the window resets.
2. Add pacing: sleep briefly between API calls so the sustained rate stays under the limit. Expected: requests flow without 429s.
3. On a 429, back off exponentially with jitter and retry; never retry immediately in a tight loop. Expected: the agent recovers instead of hammering the limit.
4. Replace per-report detail calls with list or batch endpoints that return many reports per request. Expected: far fewer requests for the same coverage.
5. Track request counts per window in the agent so it throttles itself before the API does. Expected: the agent stays under the limit proactively.

When to use

• An agent gets 429s mid-audit on large volumes.
• The run was progressing fine before the limit hit.

When not to use

• The API rejects the credential (authentication issue, not rate limiting).
• A single request fails (debug that request, not the rate).

Tool compatibility

• Expensify, Concur, Ramp, Brex APIs; standard 429 handling.

Variant phrasings

429 too many requests during audit

The HTTP-level phrasing of the same limit.

API quota exceeded mid-run

The quota-flavored wording of the same problem.

Why it happens

Audit agents are bursty: they fire hundreds of requests as fast as possible. APIs protect themselves with per-minute or per-hour caps, and the burst trips the cap partway through the run.

Provenance

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

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

Thread query: rate limit error hit mid-audit when agent tried checking 2000 reports

TL;DR: The agent's request rate exceeded the expense API's limit mid-run. Add request pacing (a small delay between calls), exponential backoff with jitter on 429 responses, and use batch or list endpoints instead of one call per report.

Not specified by the original author.

Fix agent hitting Salesforce API rate limit mid account setup run

TL;DR

The agent trips Salesforce's API limits mid-run because setup hammers the API without pacing. Batch API calls, respect the limit headers, and checkpoint progress so the run resumes cleanly. Salesforce limits are org-wide, so the agent shares them with every other integration.

The error

Agent failed
Salesforce API rate limit hit mid account setup run. Setup incomplete.

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=agent hit salesforce api rate limit mid account setup run failed"

Fix it

Step 1: Checkpoint completed work

Record which accounts finished setup before the limit hit.

Expected: A resume continues instead of redoing work.

Step 2: Read the limit headers

Check the API usage headers on responses to see remaining calls.

Expected: You know how close to the ceiling the org runs.

Step 3: Batch and pace the calls

Use composite or bulk APIs where possible and add pacing between calls.

Expected: Call volume drops dramatically.

Step 4: Add backoff on limit errors

On limit errors, wait and retry with backoff instead of failing.

Expected: Transient limits clear without killing the run.

Step 5: Resume and verify

Resume the run from the checkpoint.

Expected: All accounts finish setup with no duplicates.

When this applies

• Agents hit Salesforce API limits during setup runs
• Bulk Salesforce operations die partway
• You are building Salesforce automation agents

When it doesn't

• The error is about permissions (check the connected app scopes)
• Single calls fail (check the call itself)
• Limits hit with no agent running (another integration is the culprit)

Compatibility

Salesforce REST and Bulk APIs. Org-wide API limits.

Variant phrasings

salesforce api limit agent setup

Same failure. Batching plus pacing plus checkpoints is the fix.

agent rate limited salesforce bulk

Bulk API exists for exactly this. Use it instead of one-by-one REST calls.

salesforce 403 rate limit exceeded agent

Salesforce signals limits distinctly. Back off on that signal, not on all errors.

Why it happens

Salesforce enforces org-wide API call limits shared across all integrations. A setup agent firing rapid sequential calls consumes the budget fast, and when it is gone, everything fails. The agent must treat API calls as a budgeted resource.

Edge cases

• Other integrations share the budget; coordinate heavy jobs across teams
• The Bulk API has its own limits and job lifecycle; monitor job state, not just call counts
• Caching describe and metadata calls saves a surprising amount of budget

If it still fails

• Reproduce with a minimal run: one user, one file, one step.
• Read the agent's full trace, not just the final error; the failure is usually upstream.
• Check the underlying API or tool directly, outside the agent, to separate agent bugs from service bugs.
• Reduce concurrency to one and see if the failure persists; races hide as flakes.
• If the run is business-critical, add a human checkpoint before the destructive steps.

Prevention

• Checkpoint long runs so any failure resumes instead of restarting.
• Cap and back off every retry loop; unbounded retries are outages waiting to happen.
• Validate inputs at each pipeline stage; fail fast with clear errors.
• Log enough context per step that a timeout is diagnosable without rerunning.
• Give destructive steps a human checkpoint or a dry-run mode.

Provenance

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

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

Thread query: agent hit salesforce api rate limit mid account setup run failed

TL;DR: The agent trips Salesforce's API limits mid-run because setup hammers the API without pacing. Batch API calls, respect the limit headers, and checkpoint progress so the run resumes cleanly. Salesforce limits are org-wide, so the agent shares them with every other integration.