You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to save new works and datasets on Staging results in the "Something is not working on our end" error. I also encountered the error approving a new work. It has been intermittent whether the changes are actually saved in spite of the error.
Expected behavior
Click Save (on new deposit or edits, regardless of review stage) and the work is saved.
Actual behavior
I encountered this while doing QA for removal of the DOI plugin, working with Datasets on staging.
Created a new test dataset work on staging. Tried to save and got the "Something is not working on our end" error. The test work was not saved.
Tried editing an existing dataset work and saving. Errored on save. The changes were not saved.
Tried creating a new test work in a different work type. Errored on save but it DID save the work (but not the file).
I approved this work, and it errored again but also completed the approval.
After it was approved and deposited, I was able to edit and save without error twice, including a metadata-only update and adding a file.
Tried editing an existing non-dataset work. Saved without error.
Descriptive summary
Trying to save new works and datasets on Staging results in the "Something is not working on our end" error. I also encountered the error approving a new work. It has been intermittent whether the changes are actually saved in spite of the error.
Expected behavior
Click Save (on new deposit or edits, regardless of review stage) and the work is saved.
Actual behavior
I encountered this while doing QA for removal of the DOI plugin, working with Datasets on staging.
Steps to reproduce the behavior
Create a new work on Staging and save it.
Related work
The text was updated successfully, but these errors were encountered: