500 gets returned to user when data is not found in azure or aws

[BobanL]

Description

• When something isn't found in aws blob storage or s3 a 500 internal server error is returned to the user

Steps to reproduce

List out the steps in detail to reproduce the bug

1. Run with azure/s3
2. View any non-existent id

Expected Result

• 404 screen should appear

Actual result

• 500 error is displayed
  
  

Priority

Provide an estimate for level of impact the bug has today by placing an X in the applicable bracket

Priority

• Low priority The bug does not have to be fixed immediately. High and medium priority bugs should be addressed first.
• Medium priority Typically, medium-priority bugs do not affect customers directly and therefore can be fixed in the normal course of testing and development.
• High priority High priority bugs must be addressed immediately. They often affect the app’s functionality and impact customers and their user experience. They must take priority.

Notes

Include any additional context or information here that doesn't fit into other parts of the template