After updating to the latest version, it keeps showing the message "Workflow graph might have been modified, please refresh and resubmit." And I am unable to save.

[Mgrsc]

Self Checks

• [X] This is only for bug report, if you would like to ask a question, please head to Discussions.
• [X] I have searched for existing issues search for existing issues, including closed ones.
• [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [X] Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.8

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Open the created application, then click on "Publish Update" to trigger a pop-up.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot[bot]]

To address the issue where Dify 0.6.8 shows "Workflow graph might have been modified, please refresh and resubmit," it's crucial to ensure your setup is correctly configured. This error typically points to a problem with state management or data consistency. Here are targeted steps to resolve this:

1. Service Configuration: Check that all services, especially those managing workflows and states, are correctly configured. This includes database, Redis, and workflow management services.

2. Database Migrations: Make sure MIGRATION_ENABLED is true for the API service, allowing automatic database schema updates.

3. Redis Configuration: Verify Redis is correctly linked to the API and worker services, as it's key for state and session management.

4. Network Configuration: Ensure all necessary services are attached to the correct Docker networks, as defined in your Docker Compose file.

5. Logs: Review Docker container logs for any errors that might indicate what's causing the inconsistency.

6. Session Management: Confirm the SECRET_KEY for session cookies is consistent across services.

7. CORS Settings: If using different domains for the API and frontend, adjust WEB_API_CORS_ALLOW_ORIGINS and CONSOLE_CORS_ALLOW_ORIGINS to allow cross-domain requests.

8. Vector Store Access: If applicable, ensure vector store services are correctly configured and accessible.

9. Nginx Configuration: For setups using Nginx as a reverse proxy, check that it's properly routing requests to the API and web services.

10. Environment Variables: Double-check all environment variables for accuracy, particularly those related to service URLs.

For more detailed configuration guidance, refer to the Docker Compose configuration file in the Dify repository. If these steps don't resolve the issue, refreshing the workflow graph and resubmitting, as the error suggests, is a known workaround.

Details

Sources

• docker/docker-compose.yaml
• api/controllers/console/app/error.py

About Dosu This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

[takatost]

pls make sure the api and web service versions are consistent.

[hjlarry]

I encountered the same issue which was resolved by docker pull langgenius/dify-web:latest upgrade the web container

[Mgrsc]

pls make sure the api and web service versions are consistent.请确保 API 和 Web 服务版本一致。

Thank you for indeed fixing it

[Mgrsc]

I encountered the same issue which was resolved by docker pull langgenius/dify-web:latest upgrade the web container我遇到了同样的问题，通过 docker pull langgenius/dify-web:latest 升级 Web 容器解决了。

Thank you for indeed fixing it