Skip to content

Missing function - retry mechanism against HTTP 429Β #315

@barrack1234

Description

@barrack1234

We are having issues with MasterCard provider which doesn't have retry mechanism against server's HTTP 429 "Too Many Requests" responds. Especially that would become very handy when dealing with API endpoints where throttling limit is not so generous like 1 request per sec allowed (as in this example: https://learn.microsoft.com/en-us/graph/throttling-limits#identity-protection-and-conditional-access-service-limits). I know there is a rate_limit that can be set it up, but MasterCard provider is not the only one interacting with mentioned endpoints so it returns 429 errors. Retry mechanism is a must when considered the same API endpoints is being used with other providers or even GUIs.
Have a great day.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions