Skip to content

bug: Error Handling in the Retryer #4342

@ShubhamDeshmuk-h

Description

@ShubhamDeshmuk-h

Describe the bug

Issue: In src/common/retryer.js, if an error occurs and it is not a "bad credentials" or "account suspended" error, the code returns err.response instead of throwing or handling the error.

This can lead to unexpected behavior downstream, as the calling code may expect a valid response object but instead gets an error response, possibly missing required fields.

Expected behavior

it should consider always throwing an error for non-recoverable cases, or standardize the error object returned.

Screenshots / Live demo link

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions