seeing 5xxs codes, mostly for URI `/pf/api/v3/content/fetch/...
This is an externally hosted service, and in this case it was returning 204s. It appears Fusion currently treats these as 5xxs, which triggers alerts. Ideally, Fusion would treat a 204 as a valid response, perhaps with an empty result set.
Guest
The platform doesn't want to make the assumption that no content correlates to an empty object or array.
Given that there is no data to be used by the component, there are two options available on the platform:
1) Change the external API to return a 200 and an empty object
or
2) Update the content service code to make the http call and handle the 204 internally
The issue is that a 204 with no body will fail to parse so it will result in a 500 and we will serve stale from our content cache for 24 hours.
Workaround:
If they would like to use 204’s they should update from using fetch to using a content source that does a resolve and makes the request themselves.