Skip to content

log headers if 429 encountered #515

@whoabuddy

Description

@whoabuddy

This would've helped a lot diagnosing the last round of issues - 429 can mean we're hitting it too fast OR that we've hit a monthly quota, and the headers return more info about both.

If we just default to raising a logger.warn() every time we hit a 429 then the extra info will be easy to pinpoint right away.

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