Blank
Umbraco Status page
Umbraco Status page
Welcome to the Umbraco status page. On this page, you can see the current operational status as well as plans for scheduled maintenance and automatic upgrades for all our cloud offerings: Umbraco Cloud and Heartcore.
Subscribe to updates above to get the latest status send straight to your inbox.
If you’re experience issues with your cloud project which does not seem to relate to the current operational status, please go to Our Umbraco and search for the issue or reach out to the Umbraco Support in the portal chat.
Heartcore: Issue with GraphQL schema update causing certain query combinations to not work
Incident
Report for Umbraco Cloud
Resolved
On August 15th we rolled out an update for the part of our GraphQL Server, which generates the types that make up the GraphQL schema for all Umbraco Heartcore Projects. The update was deployed at 8:00am August 15th and the GraphQL schemas were updated in the evening around 10:00pm. This update included support for complex filtering for complex types like the content picker, media picker and multinode tree picker. After the schemas were updated across all Heartcore projects we saw that certain combinations of using the media picker in nested content returned null instead of the url to the media.
While only a subset of projects were affected we quickly isolated the issue to the schema generation, rolled back the deployment and started updating the schemas again. Once that was completed we verified the affected queries yielded the correct results before closing the issue at around 1:00am august 16th.
We apologies to all affected by this regression issue in the GraphQL schema generation. We know that for some it was very late in the evening, which is never fun when having to wait for a resolution. Please note that the Heartcore Product team takes these types of issues very serious, and as a result we are expanding our testing efforts around GraphQL and REST API updates.
There will be hard requirements for running tests in both development and staging with a large selection of data-sets and queries that correspond to current users of Umbraco Heartcore.
// The Umbraco Heartcore Product team
While only a subset of projects were affected we quickly isolated the issue to the schema generation, rolled back the deployment and started updating the schemas again. Once that was completed we verified the affected queries yielded the correct results before closing the issue at around 1:00am august 16th.
We apologies to all affected by this regression issue in the GraphQL schema generation. We know that for some it was very late in the evening, which is never fun when having to wait for a resolution. Please note that the Heartcore Product team takes these types of issues very serious, and as a result we are expanding our testing efforts around GraphQL and REST API updates.
There will be hard requirements for running tests in both development and staging with a large selection of data-sets and queries that correspond to current users of Umbraco Heartcore.
// The Umbraco Heartcore Product team