Closed FuhuXia closed 9 months ago
Handle 500 error gracefully
Previously there was a 500 graceful error page. That was lost during the cloud.gov migration. Possibly tied to NGINX config.
Here's a screenshot of what I'm seeing.
checked those datasets are in a collection, but the parent is deleted.
FYI. The UI display for datasets have valid parent collection:
The error returned when the parent collection was not found. To address this, we implemented error handling and have the following options for UI changes for this situation:
Maintain the current display format but include a message indicating that the parent collection does not exist.
Enhance the display by adding a link to search for sibling datasets within the same collection.
Completely omit the 'Collection' section from the display in this scenario.
Furthermore, will do additional research to understand how the harvester behaves when harvesting dataset without a parent collection existing.
After discussing with the team, we have decided to resolve the 500 error by implementing the following UI changes:
Additionally, created a new ticket (https://github.com/GSA/data.gov/issues/4594) to implement the necessary logic to prevent the deletion of the parent collection during the harvesting stage.
After pushed the change to catalog, double checked on catalog production, the error from the missing parent issue is fixed.
Some dataset returns 500 error with error message
How to reproduce
" 500 " NginxLog
in NewRelic on app catalog-proxy for more examples.Expected behavior
200 or 404 response code
Actual behavior
500 response code
Sketch
[Notes or a checklist reflecting our understanding of the selected approach]