Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Retry system should fail sooner on errors that will never be resolved #104

Open
nmassey001 opened this issue Apr 18, 2024 · 1 comment
Open

Retry system should fail sooner on errors that will never be resolved #104

nmassey001 opened this issue Apr 18, 2024 · 1 comment
Assignees
@nmassey001

Comments

@nmassey001
Copy link
Contributor

At the moment the retry system will retry 6 times for an error that will never be resolved - for example, if the wrong credentials for the object storage are provided. 6 retries will be attempted over the course of 5 days. This will be very frustrating for the user.

The retry system should recognise errors that will not be resolved and fail straight away.
@nmassey001 nmassey001 self-assigned this Apr 18, 2024
@nmassey001 nmassey001 moved this to Deployment Backlog in NLDS Project Board Apr 18, 2024
@nmassey001
Copy link
Contributor Author

Should refactor the retry lists into classes that can be instantiated within the consumers.

@nmassey001 nmassey001 moved this from Deployment Backlog to Refactor backlog in NLDS Project Board May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nmassey001 nmassey001

Labels
None yet
Projects
NLDS Project Board
Status: Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nmassey001