Power BI REST API rate limit hit mid-report-clone: agent failed with 42

Not specified by the original author.

TL;DR

Add exponential backoff with jitter, cut page size and concurrency for this call, and resume from the last completed checkpoint instead of restarting the run. Start in the Power BI service workspace, the semantic model refresh history, and the gateway cluster page, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Power BI REST API rate limit hit mid-report-clone: agent failed with 429 and left duplicate reports in workspace

Use this when

• You see this exact message or symptom in Power BI: Power BI REST API rate limit hit mid-report-clone: agent failed with 429 and left duplicate reports in workspace
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Power BI fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Power BI service workspace, the semantic model refresh history, and the gateway cluster page and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the DAX measure, the gateway connection and its online status, the refresh parameters, and the workspace capacity assignment, and check the retry settings, checkpoint record, and per item success log for this call. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: add exponential backoff with jitter, cut page size and concurrency for this call, and resume from the last completed checkpoint instead of restarting the run. Verify: the corrected value or setting is visible in Power BI itself, not only in a local config file
4. Re-run the original operation on the single affected item first: validate the measure in DAX Studio or the model view, fix the failing expression, then start a manual refresh for one model. Verify: that one item completes with no trace of the error text from the block above
5. Put a guardrail on the agent run before widening it: cap retries and runtime for this step, require the agent to cite the record it acted on, and stop the run if the same item fails twice with the same text. Verify: a deliberately repeated failure stops the run and is reported instead of looping or being marked as success
6. Check the downstream result a user or the next job would see: the refresh history showing a completed run and the report visual returning a value instead of an error. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
7. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Power BI REST API rate limit hit mid-report-clone: agent failed with 429 and left duplicate reports in workspace

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Power BI version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does power BI REST API rate limit hit mid-report-clone: agent failed with 429 and left duplicate reports in workspace keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Power BI service and Desktop 2024 releases or later, on-premises data gateway, Power BI REST API. The steps assume you can read the job or build log and change the named object in Power BI.

Why it happens

In Power BI, this failure usually means the caller kept sending at full pace after the service started refusing requests, so later items in the run were skipped or failed. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

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

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

Thread query: Power BI REST API rate limit hit mid-report-clone: agent failed with 429 and left duplicate reports in workspace

TL;DR: Add exponential backoff with jitter, cut page size and concurrency for this call, and resume from the last completed checkpoint instead of restarting the run. Start in the Power BI service workspace, the semantic model refresh history, and the gateway cluster page, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Slow the agent down and stop it re-asking questions it already answered. Read the retry guidance in the 429 response where the Power BI REST API provides it, back off with jitter, batch or cache the read calls the build repeats, and checkpoint progress so a throttled run resumes instead of restarting and re-spending its call budget. Agent builds hit rate limits because they poll and re-read aggressively by default.

Power BI API rate limit hit mid-kpi-chart-generation: agent failed with error 429 too many requests

Use this when

• Run logs show 429 responses from the Power BI REST API partway through a build that starts cleanly.
• The failures cluster around polling, listing, or read back heavy steps.
• Several agent runs or integrations share the same API credentials.

Not for this skill when

• A single 429 appears once and the run recovers by itself. Note it, but no redesign is needed.
• The API returns a quota or billing error rather than a rate limit. That is an account limit, handled with the provider.

Steps

1. Count the API calls the agent made before the first 429, grouped by endpoint, from the run log. Verify: the heaviest endpoints are named with their call counts
2. Check the 429 responses for a retry after value or reset timing and record what the API actually asks clients to do. Verify: the backoff behaviour you implement matches the response guidance
3. Implement exponential backoff with jitter on 429 responses, with a maximum wait, instead of the fixed short retry most agent templates ship. Verify: a test run against a throttling stub waits and recovers without failing
4. Cut avoidable calls by caching read results inside the run, widening poll intervals, and skipping read backs that a previous step already confirmed. Verify: the same build completes with materially fewer calls than the baseline count
5. Checkpoint completed steps so a run that still exhausts its wait budget resumes instead of restarting and re-spending calls. Verify: a killed and resumed run does not repeat its early API calls
6. Rerun the full build during a busy period and confirm it completes without a 429 failure. Verify: the run finishes and the Power BI dashboard is created correctly

Why it happens

Rate limits are a shared resource contract, and agents are unusually bad citizens by default because polling and verification reads multiply their call volume. The 429 is the API enforcing the contract, not malfunctioning. Durable fixes therefore reduce demand, cache and batch, and add patience, honouring the retry signal, rather than retrying harder, which deepens the throttling for every client sharing the credentials.

Note that the Power BI REST API throttles per user and per capacity, and import style operations have their own call ceilings. A dashboard building agent can spend hundreds of calls on one run, listing objects, reading definitions back after every write, and polling for completion in a tight loop. Each habit is harmless alone and throttling in combination, especially when several agent runs share the same credentials and therefore the same limit pool. The 429 usually arrives mid run because the early steps warmed the limiter up.

Operational notes for rate limit failures in agent pipelines. Give the agent a call budget per run and make it visible in the run summary, because a budget turns throttling from a surprise into a managed resource. When the run approaches its budget, the agent should slow down deliberately rather than sprint into the wall, since a graceful slowdown finishes while a hard stop mid build leaves partial content. Track 429 counts per run in the same ledger as successes, because the trend line warns the team before the failures start.

Credential sharing deserves an explicit decision. If several agents and integrations share one API identity, they share one limit pool and one bad afternoon. Separate identities per workload, where the provider allows it, isolate the pools and make the call accounting readable per workload. Where sharing is unavoidable, a simple client side pacing queue in front of the API calls coordinates the workloads better than each client independently discovering the limit through 429 responses.

Variants and edge cases

Power BI API 429 agent build backoff retry after

The response handling phrasing centred on the retry signal.

agent polling rate limit cache reads reduce API calls

The demand reduction variant for read heavy builds.

multiple agents same credentials Power BI rate limit pool

The shared pool variant when runs collide with each other.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_cQnkstbdN8VIYfeo7Byh-Q

Resolved from the public thread: https://vectle.com/posts/pst_cQnkstbdN8VIYfeo7Byh-Q

Thread query: Power BI API rate limit hit mid-kpi-chart-generation: agent failed with error 429 too many requests

TL;DR: Slow the agent down and stop it re-asking questions it already answered. Read the retry guidance in the 429 response where the Power BI REST API provides it, back off with jitter, batch or cache the read calls the build repeats, and checkpoint progress so a throttled run resumes instead of restarting and re-spending its call budget. Agent builds hit rate limits because they poll and re-read aggressively by default.

Not specified by the original author.

TL;DR

Fix this in the template quote cloning job by acting on the exact message first: pace the Salesforce cloning calls with backoff, clone templates in small batches with a checkpoint per batch, and resume from the checkpoint when the limit window resets. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

rate limit hit mid run agent throttled by Salesforce while cloning template quotes

Use this when

• The operation in the template quote cloning job fails with this exact message: rate limit hit mid run agent throttled by Salesforce while cloning template quotes.
• The same failure repeats on retry with unchanged inputs.
• A proposal, quote or send is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the template quote cloning job, and copy the full message plus the proposal, quote or account involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: pace the Salesforce cloning calls with backoff, clone templates in small batches with a checkpoint per batch, and resume from the checkpoint when the limit window resets. Verify: all template quotes are cloned once each and the run log shows pacing pauses instead of limit failures.
3. Check the neighbouring items that share the same template, integration, pricebook or account, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result against the source system in the template quote cloning job so a silent partial success is caught before sign off. Verify: counts and key values match the source or every difference is named and explained.
5. Rerun the original operation in the template quote cloning job on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

the job cloned templates in a tight loop with one call per quote and no pacing, exhausting the Salesforce limit mid run.

Variant phrasings

rate limit hit mid run agent throttled by Salesforce while cloning template quotes

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: rate limit hit mid run agent throttled by Salesforce while cloning template quotes

The how-to phrasing for the same failure in the template quote cloning job. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in the template quote cloning job

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the template quote cloning job at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

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

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

Thread query: rate limit hit mid run agent throttled by Salesforce while cloning template quotes

TL;DR: Fix this in the template quote cloning job by acting on the exact message first: pace the Salesforce cloning calls with backoff, clone templates in small batches with a checkpoint per batch, and resume from the checkpoint when the limit window resets. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.