When a user raises an exception with their job and it fails to complete, that exception should somehow be passed to the user in an email (current behavior is the job execution simply stops, and user receives no communication that their job failed). This also may require implementing a set of MORF exception classes, but initially, we can just pass the raw exception to a user.
This also requires doing some knid of checking to ensure that users are not exposing any underlying aspects of the data in their job. One way to do this would be to not include any output from their image, and to only include errors directly from the server. We could also just indicate the type of error/exception, not the actual content of the erorr message (but this might make it more difficult for users to discern the problem.)
When a user raises an exception with their job and it fails to complete, that exception should somehow be passed to the user in an email (current behavior is the job execution simply stops, and user receives no communication that their job failed). This also may require implementing a set of MORF exception classes, but initially, we can just pass the raw exception to a user.
This also requires doing some knid of checking to ensure that users are not exposing any underlying aspects of the data in their job. One way to do this would be to not include any output from their image, and to only include errors directly from the server. We could also just indicate the type of error/exception, not the actual content of the erorr message (but this might make it more difficult for users to discern the problem.)