Closed mikkonie closed 1 month ago
This might be related to #1894. To be looked into..
This may be the case of admin(s) updating things stuck due to iRODS problems and failing to update timeline status manually. See dsicussion in #1894. I'm setting this to ongoing
for now and I'll keep an eye out of further occurrences.
I've observed this happening again, during a time when no iRODS issues were reported.
One moving part which may aid in reproducing: the iRODS collections had been created for the sheets.
Bingo! This fails if iRODS collections exist for the investigation. If no collections have been created, timeline is updated appropriately.
Updating the description and tagging this for v1.0.0.
Fixed.
I noticed this in our production server logs. A user has initiated sheet deletion and a
sheet_delete
timeline event is created, but it ends with theSUBMIT
status.As far as I can see, the deletion has actually gone through and the project has been in a normal state afterwards, but still, this should not happen.
Update: This happens only if iRODS collections are to be created. This means something probably goes wrong in the related taskflow. To be investigated for v1.0.0.