Help🙏🙏🙏. Aborted: Maximum execution time exceeded: 1200.3s > 1200s

[dabaisuv]

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.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

When I'm executing a complex workflow in the debug interface, it interrupts and displays the message: "Aborted: Maximum execution time exceeded: 1200.3s > 1200s" after 1200 seconds. I've searched the documentation, GitHub issues, and browsed all the pages on Deify, but I can't find where to set this parameter. I hope I can configure it; am I missing something? 🙏🙏🙏🙏🙏

2. Additional context or comments

No response

[dosubot[bot]]

Hi @dabaisuv! I'm Dosu and I’m helping the dify team.

You can increase the workflow execution timeout by setting the WORKFLOW_MAX_EXECUTION_TIME environment variable. This variable controls the maximum allowed execution time (in seconds) for a single workflow. By default, it's set to 1200 seconds.

To change it, edit your .env file or the environment section in your docker-compose.yaml and set a higher value, for example:

WORKFLOW_MAX_EXECUTION_TIME=3600

Then restart your Dify containers for the change to take effect. This will allow longer-running workflows before hitting the timeout limit. The relevant configuration is documented in the codebase and .env.example file, and enforced in the workflow engine logic (source, source).

To reply, just mention @dosu.

---

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