Skip to content

[Feature]: Make Invoke-AzRestMethod handle throttling 429 #27752

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
o-l-a-v opened this issue May 13, 2025 · 0 comments
Open

[Feature]: Make Invoke-AzRestMethod handle throttling 429 #27752

o-l-a-v opened this issue May 13, 2025 · 0 comments
Labels
Azure PS Team customer-reported feature-request This issue requires a new behavior in the product in order be resolved. Tracking We will track status and follow internally

Comments

@o-l-a-v
Copy link

o-l-a-v commented May 13, 2025

Description of the new feature

Would be useful if the Invoke-AzRestMethod cmdlet could handle throttling / error code 429. As in try again after the given waiting time.

{
  "error": {
    "code": "429",
    "message": "Too many requests. Please retry."
  }
}

Related:

Proposed implementation details (optional)

No response

@o-l-a-v o-l-a-v added feature-request This issue requires a new behavior in the product in order be resolved. needs-triage This is a new issue that needs to be triaged to the appropriate team. labels May 13, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added customer-reported needs-triage This is a new issue that needs to be triaged to the appropriate team. and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels May 13, 2025
@isra-fel isra-fel added Azure PS Team Tracking We will track status and follow internally and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure PS Team customer-reported feature-request This issue requires a new behavior in the product in order be resolved. Tracking We will track status and follow internally
Projects
None yet
Development

No branches or pull requests

2 participants