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.11.2

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

1. Build the Dify web image locally using the official Dockerfile.

2. Set the following environment variable for the web container:

   NEXT_PUBLIC_TEXT_GENERATION_TIMEOUT_MS=6000000 

3. Do not set TEXT_GENERATION_TIMEOUT_MS.

4. Start the web container.

5. Trigger a text generation request that runs longer than 60 seconds.

✔️ Expected Behavior

If NEXT_PUBLIC_TEXT_GENERATION_TIMEOUT_MS is explicitly defined, the web frontend should respect this value and use the configured timeout.

At minimum, an explicitly set NEXT_PUBLIC_* environment variable should not be overridden by an empty value during container startup.

❌ Actual Behavior

During container startup, entrypoint.sh exports:

export NEXT_PUBLIC_TEXT_GENERATION_TIMEOUT_MS=${TEXT_GENERATION_TIMEOUT_MS} 

When TEXT_GENERATION_TIMEOUT_MS is unset, this line overwrites the existing
NEXT_PUBLIC_TEXT_GENERATION_TIMEOUT_MS with an empty value.

As a result, the frontend falls back to the default timeout (~60000 ms), and the web UI consistently times out at around 60 seconds, even though NEXT_PUBLIC_TEXT_GENERATION_TIMEOUT_MS was provided.

This happens even when the image is built locally with the official Dockerfile and is not related to custom startup scripts.