Skip to content

Implement 429 Error Handling in report-harvester #13

Description

@WildfootW

#3
When mops-crawler exceeds the rate limit of MOPS, it encounters a 429 error, leading to service disruption. The task involves implements a retry logic (maybe with exponential backoff?)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions