cstarcher
commented
1 month ago Related #1882 Related #1838
Open cstarcher opened 1 month ago
cstarcher
commented
1 month ago Related #1882 Related #1838
cstarcher
commented
1 month ago 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.
cstarcher
commented
1 month ago 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 message: Submission not found
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.