microsoft / microsoft/powerbi-powershell
Handle 429 error on Invoke-PowerBIRestMethod
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 413
- Forks
- 134
- Avg merge
- 33m
- Merged PRs (30d)
- 1
Description
Some API's have throttling a great enhancement would be a switch parameter on the "Invoke-PowerBIRestMethod" to automatically handle the 429 errors:
Invoke-PowerBIRestMethod -handleThrottleException
On a 429 error the cmdlet will automatically sleep the Retry-Seconds and execute the API again in the end handling the token expiration.
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 at the Invoke-PowerBIRestMethod entry point and inspect how REST errors, Retry-Seconds, and token expiration are currently handled. Define the retry behavior for HTTP 429 responses and confirm that the cmdlet retries after the requested delay and completes authentication handling without changing other errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100