microsoft / microsoft/powerbi-powershell
Throttling when repeatedly using Export-PowerBIReport
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 413
- Forks
- 134
- Avg merge
- 33m
- Merged PRs (30d)
- 1
Description
We have a process in which we download all reports from our tenant and check them into source control. Our process will loop all workspaces and retrieve all reports from each workspace.
Starting a few months ago, the process would fail after a number of reports have been downloaded.
We receive the following error (in our logs):
Operation returned an invalid status code '429'
Is there a workaround for this error?
sample code snippet:
`
try
{
Export-PowerBIReport -Id $report.Id -Outfile $reportFullPath -WorkspaceId $workspace.Id
} catch
{
$_.Exception
}
`
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported Export-PowerBIReport call and the loop over workspaces and reports. Reproduce the sequence that eventually returns HTTP 429, then inspect the cmdlet's handling of throttling and the available Power BI export guidance. Done means identifying and documenting a verified workaround or a concrete fix for repeated exports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100