I have run into an issue on a Hearcore project where the graphQL schema doesnt seem to get updated when deploying changes to the next enviroment (i.e. staging to live)
I have been working around this in the mean time by going through all the doc types one by one and clicking save, but thats a less than ideal solution.
Is this just a bug in heartcore? is there a way to regenerate the whole graphQL schema?
If that doesn't match with what you've experienced then please reach out to our support team via the Cloud portal and they'll be able to investigate the issue to get it resolved :)
Try saving and publishing the document type in the new environment followed by a content item that uses that document type. This technique worked for me a few times.
The Graphql schema update can take a little while to flow through.
GraphQL schema not updating after deployment
Hi Everyone,
I have run into an issue on a Hearcore project where the graphQL schema doesnt seem to get updated when deploying changes to the next enviroment (i.e. staging to live)
I have been working around this in the mean time by going through all the doc types one by one and clicking save, but thats a less than ideal solution.
Is this just a bug in heartcore? is there a way to regenerate the whole graphQL schema?
Hi Scott
Please, check our status page first, as we ran maintenance on Heartcore yesterday - https://status.umbraco.io/incidents/1h0nb551db24
If that doesn't match with what you've experienced then please reach out to our support team via the Cloud portal and they'll be able to investigate the issue to get it resolved :)
Hi Scott,
Try saving and publishing the document type in the new environment followed by a content item that uses that document type. This technique worked for me a few times.
The Graphql schema update can take a little while to flow through.
Regards, Tom.
is working on a reply...