-
Notifications
You must be signed in to change notification settings - Fork 34
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
Errors #1952
Comments
Examples of errors reported by TDL:
Comment from TDL: We see from many different Vireos...my guess is this would be either a spurious error, or it is having trouble displaying the action log? For this error there is no submission number so I can't link it to any other errors.
Comment from TDL: This I'm pretty sure is a connection problem when someone is uploading. For quite a few of these I've then gotten on the Vireo, looked at the submission and didn't see the file I expected. This seems like a real error.
Comment from TDL: These almost always deal with a field of some sort, not always update, but sometimes remove etc. If this is real, maybe someone trying to modify keywords or something else multiple maybe.
Comment from TDL: But validate is always a 400 and not a 500.
Comment from TDL: Anything related to status is always a 500 error. |
More examples from TDL:
Comment from TDL: That one was odd because of the -1.
Comment from TDL: I got this one twice from Baylor, and is one of the very rare ones with so much explanation for a 500 error.
channel: submission/get-one/25302
|
It would also be helpful for TDL and any other entity that deploys multiple Vireo instances to have a designation of which system is reporting the error included in the email. |
Related #1978 |
Describe the bug
Errors seem to be reported through the UI and support emails that cannot be attributed to errors in functionality in the system.
Expected behavior
An error should only be reported when an actual error in the system occurs.
Additional context
I've constructed this issue to be broadly defined to consolidate potential related error reporting issues in case it may be advantageous to address them all at the same time. Please add any examples of the described behavior above in the comments.
The text was updated successfully, but these errors were encountered: