Resolved
The issue affecting the content service API has been fully resolved. All systems are now operational.
Investigating
Root cause identified - a fix is being pushed to production.
Investigating
When the new content relationship feature used in combination with our route resolver it can cause the API to fail and return 500 errors.
Investigating
We are currently investigating an issue affecting content service API. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. :rocket: Next Update Expected: 30 minutes Thank you for your patience!
