Skip to content

Handle 429 (with optional Retry-After header field) by retrying #878

@yarikoptic

Description

@yarikoptic

The use case came up in

and was addressed by making rate limiting more liberal on our service. But I would not be surprised if we hit that one too eventually. IMHO viv should handle those responses gracefully and implement some sensible retry policy.

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