General DiscussionThe application ran successfully, but the log status was not updated

[lxh-code]

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

Here we can see that it has been successfully executed！However, upon closer inspection, its status is still "RUNNING" and has not been updated！ What should I do to solve this problem？

[dosubot[bot]]

Hi @lxh-code! I'm Dosu and I’m helping the dify team.

The workflow status in Dify should automatically update from "RUNNING" to "SUCCEEDED" (or another terminal state) when execution completes. This update is handled by backend logic: the WorkflowCycleManager calls a success handler, which updates the status and saves it to the database via the WorkflowExecutionRepository. If the status remains "RUNNING" after a successful run, common causes include: the success handler not being triggered, a failure in saving to the database (such as a DB error or a failed Celery task if using async), or the frontend displaying stale data from cache instead of the latest status from the database [source].

To troubleshoot:

• Check backend logs for any errors or exceptions during workflow completion.
• If you use Celery for async tasks, verify that your Celery workers are running and healthy, as a failed or delayed task can prevent status updates [source].
• Confirm that the database transaction for updating the workflow status is successful.
• Try refreshing the UI or clearing cache to rule out frontend data staleness.
• Test if the issue occurs for all workflows or only specific ones.

If none of these steps resolve the issue, collecting more details (backend logs, Dify version, reproducibility) will help narrow down the root cause.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[dosubot[bot]]

When you switch file storage to S3, workflow status updates in Dify should still work as usual—S3 errors typically cause node failures, not a stuck "RUNNING" status. If the workflow completes but the status doesn't update, it's usually due to issues with database persistence or Celery async tasks, not S3 itself.

Here's how to troubleshoot:

1. Check backend logs for errors during workflow completion, especially around S3 file operations, database transactions, and Celery task processing. Look for exceptions or repeated retries in the logs [source].
2. Make sure your S3 bucket is accessible, correctly configured, and has the right permissions. Test file uploads/downloads directly to confirm S3 is working [source].
3. If you use Celery for async workflow status updates, verify that your Celery workers are running and healthy. If Celery is down or misconfigured, status updates may not be saved [source].
4. Confirm your database is reachable and transactions are succeeding. Any DB errors will prevent status updates from being persisted [source].
5. Refresh the UI or clear cache to rule out frontend staleness.

If you see S3-specific errors (like permission denied, file not found, or unsupported headers), fix those first. But if S3 is working and the workflow still gets stuck as "RUNNING", focus on Celery and DB logs for clues. All significant errors are logged, so the logs should point you to the root cause.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[lxh-code]

How can I try to solve this problem? I checked the logs and found no issues

[dosubot[bot]]

Here’s a checklist to help you diagnose and potentially resolve the issue:

1. Check the workflow status directly in your database (not just the UI). If the status is still "RUNNING" in the DB, it’s a backend persistence issue; if it’s correct in the DB but wrong in the UI, it’s a frontend refresh/polling issue.
2. Refresh the workflow run page or clear your browser cache. Dify’s UI sometimes doesn’t auto-update for long-running or completed workflows—manual refresh is required to see the latest status [source].
3. Confirm if your deployment uses Celery for async status updates. If so, make sure all Celery workers are running and healthy; if Celery is down or misconfigured, status updates may not be saved even if logs show no errors [source].
4. Review your workflow configuration for edge cases—like error handling or branches that never reach a terminal node—which could leave a workflow stuck in "RUNNING" even after all nodes finish [source].
5. Double-check that your S3 integration is not causing silent node-level failures. S3 errors should cause node failures, not a stuck workflow status, but misconfigured error handling could mask these issues.

If you confirm the DB status is correct but the UI is not, it’s likely a frontend bug. If the DB status is also "RUNNING", focus on backend persistence, Celery, or workflow logic. Let me know what you find in the database and if you need help with specific config checks!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[lxh-code]

The status in the database is also running, and this issue also exists after changing to local storage

[dosubot[bot]]

If the workflow status is stuck as "RUNNING" in the database—even after switching between S3 and local storage—the root cause is almost certainly backend-related, not storage configuration. The most common reasons are: the workflow completion handler isn't being called, the database save operation is silently failing, or async persistence (via Celery) isn't working as expected [source].

Here’s what to check next:

• Confirm your Dify version and deployment mode. There are known bugs in older versions (e.g., v0.14.2 and v0.15.1) that can cause workflows to get stuck as "RUNNING" due to network disconnects or main thread termination during streaming; upgrading to the latest release is recommended if you’re on an older version [source].
• If you use Celery for async status updates, make sure your Celery workers are running and processing the workflow_storage queue. If Celery is down or misconfigured, status updates may never be persisted—even if logs look clean [source].
• Try restarting backend services to clear any stale in-memory caches from recent refactoring [source].
• Run a minimal workflow (single node, no streaming, no file storage) to see if the status updates correctly. If it does, the issue is likely in your workflow logic or error handling branches.
• If the problem persists, enable debug logging for WorkflowCycleManager and WorkflowExecutionRepository to catch silent failures or missed status transitions.

If you can share your Dify version, deployment details, and whether you use streaming mode or Celery, I can help you narrow it down further.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[lxh-code]

This issue arose after I changed the file storage from Dify to S3. How should I troubleshoot the problem