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.

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 saving some works on Staging #2703

Closed
carakey opened this issue Dec 20, 2024 · 0 comments · Fixed by #2704
Closed

Errors saving some works on Staging #2703

carakey opened this issue Dec 20, 2024 · 0 comments · Fixed by #2704

Comments

@carakey
Copy link

carakey commented Dec 20, 2024

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.

  • 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.

Steps to reproduce the behavior

Create a new work on Staging and save it.

Related work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants