-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
Rework errorhandling #268
Comments
For now this issue is mostly ment to be a collecting container to document cases where more proper errorhandling would make sense. It will be added to priority as soon as there is enough cases to justify the workload of reviewing everything and redefining the workflows. |
returning null if database failed. may be better to return an error. could if nothing else make a better stacktrace if deciding to throw something linked to the failedafterretryexception |
As of right now there is a lot of stuff that can outright crash hera.
A lot of these cases there propably exists a better way of handling this.
So the goal should be to rework the error handling to actually handle some possible breaking points instead of just passing the exceptions to the top level.
The text was updated successfully, but these errors were encountered: