When trying to load the new pagerduty page with our existing software catalog, the page errors out due to the backend call returning a 404:
I believe the issue is we have one (or more) backstage entities that reference a PagerDuty integration key that is invalid. On this line of code, the backend API endpoint returns a 404 if there are no matches for the integration key. I think might be better to handle this data quality issue more gracefully instead of throwing an exception.
When trying to load the new pagerduty page with our existing software catalog, the page errors out due to the backend call returning a 404:![image](https://github.com/PagerDuty/backstage-plugin-backend/assets/28457/a2667781-9167-4676-bd03-9ab53951e0e7)
I believe the issue is we have one (or more) backstage entities that reference a PagerDuty integration key that is invalid. On this line of code, the backend API endpoint returns a 404 if there are no matches for the integration key. I think might be better to handle this data quality issue more gracefully instead of throwing an exception.