Skip to content

Retrying errors that can never succeed #44926

Open
Open
Retrying errors that can never succeed#44926
Assignees
g2vinay
Labels
Azure.IdentitybugThis issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK team
Milestone
2026-05

Description

@smiklos
Miklos Szots (smiklos)
opened on Apr 9, 2025

Looking into this, passing in the custom Exponential Backoff class is the better approach as mentioned above.

As, at SDK level the azure-core SDK isn't aware of exceptions thrown by dependencies/libraries downstream.

Handling custom exceptions from other libraries in azure-core will require it to take dependency on external libraries and it will be against its design.

Resolving this issue.

Originally posted by Vinay Gera (@g2vinay) in #35668

If not the core sdk then the individual dependencies like the key vault client should have their retry policies enriched with these custom errors that come from azure. I don't think it's the user who should be aware of all of these and provide a manual override as no-one want's a hanging application.

Activity

  1. github-actions
    added
    customer-reportedIssues that are reported by GitHub users external to the Azure organization.
    needs-triageWorkflow: This is a new issue that needs to be triaged to the appropriate team.
    questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
    on Apr 9, 2025
  2. Alan Zimmer (alzimmermsft)
    assigned
    Bill Wert (billwert)
    and
    Vinay Gera (g2vinay)
    on Apr 9, 2025

  3. alzimmermsft commented on Apr 9, 2025

    @alzimmermsft
    Alan Zimmer (alzimmermsft)
    on Apr 9, 2025
    Member

    Thanks for filing this Miklos Szots (@smiklos)!

    Bill Wert (@billwert), Vinay Gera (@g2vinay), could you see if this is something that could be improved by default in azure-identity, where it uses a customized RetryPolicy that doesn't lead it into retrying failures that will never succeed. Or, see if this is something that should be pushed further upstream into msal4j.

  4. Alan Zimmer (alzimmermsft)
    added
    Azure.Identity
    and removed
    needs-triageWorkflow: This is a new issue that needs to be triaged to the appropriate team.
    on Apr 9, 2025
  5. github-project-automation
    moved this to Untriaged in Azure Identity SDK Improvementson Apr 9, 2025
  6. github-project-automation
    added this to Azure Identity SDK Improvementson Apr 9, 2025
  7. github-actions
    added
    needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK team
    on Apr 9, 2025
  8. Bill Wert (billwert)
    added this to the Backlog milestone on Apr 21, 2025
  9. Josh Free (joshfree)
    unassigned
    Bill Wert (billwert)
    on May 19, 2025
  10. Josh Free (joshfree)
    moved this from Untriaged to Backlog in Azure Identity SDK Improvementson Sep 22, 2025

  11. g2vinay commented on Oct 7, 2025

    @g2vinay
    Vinay Gera (g2vinay)
    on Oct 7, 2025
    Member

    I will investigate this and get back here.

  12. Sameeksha Vaity (samvaity)
    added
    bugThis issue requires a change to an existing behavior in the product in order to be resolved.
    and removed
    questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
    on Oct 9, 2025

  13. samvaity commented on Oct 21, 2025

    @samvaity
    Sameeksha Vaity (samvaity)
    on Oct 21, 2025
    Member

    Vinay Gera (@g2vinay) Do you have an update on this?

  14. Vinay Gera (g2vinay)
    modified the milestones: Backlog, 2026-01 on Dec 11, 2025
  15. Vinay Gera (g2vinay)
    modified the milestones: 2026-01, 2026-02 on Jan 28, 2026
  16. Scott Addie (scottaddie)
    moved this from Backlog to In Progress in Azure Identity SDK Improvementson Jan 28, 2026
  17. Vinay Gera (g2vinay)
    modified the milestones: 2026-02, 2026-06, 2026-05 on May 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Azure.IdentitybugThis issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK team

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions