But there are cases for which a job fails which is not reported via an email notification and since a whole workflow is reported as “completed successfully”, a user will not find out about this issue, unless he/she makes it a habit of expanding every micro-service and every job.
This happens in case File format Identification during a transfer runs into a file format which is not put on “enabled” in the Preservation Planning (see the screenshots attached).
Although this is technically not a “failure” the outcome of this job might be critical for a user who has deliberately put that specific file format on “disabled”.
Describe the solution you'd like to see implemented
So my suggestion is to always notify a use when a workflow/transfer encounters a failure, whether critical or not.
Describe alternatives you've considered
Alternative could be to ‘flag’ the workflows/transfers which has a job which has failed as not completed successfully, i.e. red, the a user would see immediately that a workflow/transfer encountered problems, but that might be too much for most of the cases.
Additional context
I understand that dashboard users might not be eager to get more email notifications, but if the function "send system emails" in the profile of Archivematica v1.11.x dashboard users is a way to disable these kind of email notifications per user, then this is a perfect way to deal with this and then we might even consider to always send email notifications after a transfer has been concludes, which can be subdivided into three categories to be indicated in the email header:
transfer completed successfully
transfer completed successfully, but with errors
transfer failed
For Artefactual use:
Before you close this issue, you must check off the following:
[ ] All pull requests related to this issue are properly linked
[ ] All pull requests related to this issue have been merged
[ ] A testing plan for this issue has been implemented and passed (testing plan information should be included in the issue body or comments)
[ ] Documentation regarding this issue has been written and merged
[ ] Details about this issue have been added to the release notes
sallain
commented
4 years ago
Please describe the problem you'd like to be solved At the moment there are only two cases for which a dashboard user gets an email notification:
But there are cases for which a job fails which is not reported via an email notification and since a whole workflow is reported as “completed successfully”, a user will not find out about this issue, unless he/she makes it a habit of expanding every micro-service and every job. This happens in case File format Identification during a transfer runs into a file format which is not put on “enabled” in the Preservation Planning (see the screenshots attached). Although this is technically not a “failure” the outcome of this job might be critical for a user who has deliberately put that specific file format on “disabled”.
Describe the solution you'd like to see implemented So my suggestion is to always notify a use when a workflow/transfer encounters a failure, whether critical or not.
Describe alternatives you've considered Alternative could be to ‘flag’ the workflows/transfers which has a job which has failed as not completed successfully, i.e. red, the a user would see immediately that a workflow/transfer encountered problems, but that might be too much for most of the cases.
Additional context I understand that dashboard users might not be eager to get more email notifications, but if the function "send system emails" in the profile of Archivematica v1.11.x dashboard users is a way to disable these kind of email notifications per user, then this is a perfect way to deal with this and then we might even consider to always send email notifications after a transfer has been concludes, which can be subdivided into three categories to be indicated in the email header:
For Artefactual use:
Before you close this issue, you must check off the following: