Self hosting problem after rebooting machine

[github-carlos]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Content

I am hosting Dify on an EC2 instance using Docker Compose and deploying it via a Bitbucket pipeline. In my pipeline, I essentially remove all Dify-related files from the server, redeploy the application, stop the containers, and then start them again.

I've already externalized some environment variables to connect to an external database, S3 storage, and Redis. However, after each redeploy, when I try to perform a retrieval test through the front end, I encounter a "GraphQL schema not found" error. The issue resolves if I deactivate and reactivate the document, but this isn't ideal.

My question is: how can I make this process more reliable so that, even after a redeploy, the system continues to work with the existing data without issues? What might I be overlooking?

The error message is:
Query was not successful! Unexpected status code: 422, with response body: {'error': [{'message': 'no graphql provider present, this is most likely because no schema is present. Import a schema first!'}]}.; Query was not successful! Unexpected status code: 422, with response body: {'error': [{'message': 'no graphql provider present, this is most likely because no schema is present. Import a schema first!'}]}.