dify - 💡(How to fix) Fix Workflow runs indefinitely past APP_MAX_EXECUTION_TIME, stuck in "running" status [UI] [1 comments, 2 participants]

Self Checks

• I have read the Contributing Guide and Language Policy.
• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.13.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Bug Description: When a workflow is triggered, it continues running beyond the timeout value set in APP_MAX_EXECUTION_TIME (in .env). The workflow run is displayed in the UI with a running status indefinitely and never transitions to a failed or completed state.

Steps to Reproduce:

Set APP_MAX_EXECUTION_TIME to a specific value in .env (default 1200). Create a workflow that is designed to run longer than this limit (e.g., a long LLM chain or loop). Trigger the workflow via the UI or API. Observe the run status in the UI — it remains running past the configured timeout. Check the workflow_runs table in the database — it is empty. Check the Celery worker — no task record is present.

✔️ Expected Behavior

The workflow should be forcibly terminated once APP_MAX_EXECUTION_TIME is exceeded, and the run should be marked as failed with a timeout error.

❌ Actual Behavior

The workflow run stays in running status in the UI without ever resolving. No timeout error is shown. The workflow_runs table in the database contains no record of the run. The worker queue also shows no record of the run.