The email link sent by the human in loop node cannot be opened #22216

Open
opened 2026-02-21 20:16:11 -05:00 by yindo · 5 comments
Owner

Originally created by @HZJprince on GitHub (Feb 13, 2026).

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The link received by the email is /form/cn1Ti9rKDQNAx1NGwuQ0MF99
Then add the dify homepage link in front of it and it won't open, as shown in the figure below:
Image

✔️ Expected Behavior

1

Actual Behavior

1

Originally created by @HZJprince on GitHub (Feb 13, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.13.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The link received by the email is /form/cn1Ti9rKDQNAx1NGwuQ0MF99 Then add the dify homepage link in front of it and it won't open, as shown in the figure below: <img width="1113" height="876" alt="Image" src="https://github.com/user-attachments/assets/418ed432-ba27-4996-b962-06b430d665f8" /> ### ✔️ Expected Behavior 1 ### ❌ Actual Behavior 1
yindo added the 🐞 bug label 2026-02-21 20:16:11 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Feb 13, 2026):

This appears to be related to a recent instability in the human-in-the-loop feature. The human input functionality was implemented and then immediately reverted on January 30, 2026, which may have left the system in an inconsistent state where emails are still being sent but the endpoints don't work correctly.

URL format issue: The email link you received (/form/cn1Ti9rKDQNAx1NGwuQ0MF99) appears to be missing parts of the expected path. Based on the API routing code, the correct format should be:

  • https://your-domain/api/form/human_input/cn1Ti9rKDQNAx1NGwuQ0MF99

Workaround: Try accessing the form using the full API path above instead of just prepending your homepage URL.

Since the feature was recently reverted, this may be a known issue that the team is working on. You may want to watch for updates in future releases.

To reply, just mention @dosu.


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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 13, 2026): <!-- Answer --> This appears to be related to a recent instability in the human-in-the-loop feature. The [human input functionality was implemented](https://github.com/langgenius/dify/pull/31646) and then [immediately reverted](https://github.com/langgenius/dify/pull/31766) on January 30, 2026, which may have left the system in an inconsistent state where emails are still being sent but the endpoints don't work correctly. **URL format issue:** The email link you received (`/form/cn1Ti9rKDQNAx1NGwuQ0MF99`) appears to be missing parts of the expected path. Based on the [API routing code](https://github.com/langgenius/dify/blob/98466e2d29ac5146b6a3220aa5f16cded77ce30b/api/controllers/web/human_input_form.py#L68), the correct format should be: - `https://your-domain/api/form/human_input/cn1Ti9rKDQNAx1NGwuQ0MF99` **Workaround:** Try accessing the form using the full API path above instead of just prepending your homepage URL. Since the feature was recently reverted, this may be a known issue that the team is working on. You may want to watch for updates in future releases. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/a2f2efe3-386a-4b43-85b5-e5abc65b8685?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a2f2efe3-386a-4b43-85b5-e5abc65b8685?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a2f2efe3-386a-4b43-85b5-e5abc65b8685?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a2f2efe3-386a-4b43-85b5-e5abc65b8685?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a2f2efe3-386a-4b43-85b5-e5abc65b8685?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a2f2efe3-386a-4b43-85b5-e5abc65b8685?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a2f2efe3-386a-4b43-85b5-e5abc65b8685?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20appears%20to%20be%20related%20to%20a%20recent%20instability%20in%20the%20human-in-the-loop%20feature.%20The%20%5Bhuman%20input%20functionality%20was%20implemented%5D%28https%3A//github.com/langgenius/dify/pull/31646%29%20and%20then%20%5Bimmediately%20reverted%5D%28https%3A//github.com/langgenius/dify/pull/31766%29%20on%20January%2030%2C%202026%2C%20which%20may%20have%20left%20the%20system%20in%20an%20inconsistent%20state%20where%20emails%20are%20still%20being%20sent%20but%20the%20endpoints%20don%27t%20work%20correctly.%0A%0A%2A%2AURL%20format%20issue%3A%2A%2A%20The%20email%20link%20you%20received%20%28%60/form/cn1Ti9rKDQNAx1NGwuQ0MF99%60%29%20appears%20to%20be%20missing%20parts%20of%20the%20expected%20path.%20Based%20on%20the%20%5BAPI%20routing%20code%5D%28https%3A//github.com/langgenius/dify/blob/98466e2d29ac5146b6a3220aa5f16cded77ce30b/api/controllers/web/human_input_form.py%23L68%29%2C%20the%20correct%20format%20should%20be%3A%0A-%20%60https%3A//your-domain/api/form/human_input/cn1Ti9rKDQNAx1NGwuQ0MF99%60%0A%0A%2A%2AWorkaround%3A%2A%2A%20Try%20accessing%20the%20form%20using%20the%20full%20API%20path%20above%20instead%20of%20just%20prepending%20your%20homepage%20URL.%0A%0ASince%20the%20feature%20was%20recently%20reverted%2C%20this%20may%20be%20a%20known%20issue%20that%20the%20team%20is%20working%20on.%20You%20may%20want%20to%20watch%20for%20updates%20in%20future%20releases.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/32303)
Author
Owner

@HZJprince commented on GitHub (Feb 13, 2026):

I also tried the full url for this: https://your-domain/api/form/human_input/cn1Ti9rKDQNAx1NGwuQ0MF99
Still not good

@HZJprince commented on GitHub (Feb 13, 2026): I also tried the full url for this: https://your-domain/api/form/human_input/cn1Ti9rKDQNAx1NGwuQ0MF99 Still not good
Author
Owner

@kurokobo commented on GitHub (Feb 13, 2026):

To correct URL in the email, you should specify APP_WEB_URL in your .env file then stop and start the instance.

@kurokobo commented on GitHub (Feb 13, 2026): To correct URL in the email, you should specify APP_WEB_URL in your .env file then stop and start the instance.
Author
Owner

@HZJprince commented on GitHub (Feb 13, 2026):

@kurokobo After configuring the .env, the mailbox received the full URL, but it still cannot be opened
mailbox:

Image

still cannot be opened
Image

@HZJprince commented on GitHub (Feb 13, 2026): @kurokobo After configuring the .env, the mailbox received the full URL, but it still cannot be opened mailbox: <img width="1527" height="342" alt="Image" src="https://github.com/user-attachments/assets/d2694e6b-37aa-499c-9643-861af55edfe1" /> still cannot be opened <img width="2136" height="948" alt="Image" src="https://github.com/user-attachments/assets/38301898-9113-4849-8cd5-de656519f976" />
Author
Owner

@QuantumGhost commented on GitHub (Feb 14, 2026):

@HZJprince It seems like this is a deployment-related issue. To facilitate the debugging process, could you please provide the following information?

  1. Network request logs and browser console logs for the form page.
    You can collect the network logs using the following steps:

    a. Open the Chrome Developer Tools.
    b. Paste the link received in the email and navigate to the form page.
    c. Export the requests using the Export HAR (sanitized) feature, as shown in the image below:

    Image
  2. The configuration values for CONSOLE_API_URL, CONSOLE_WEB_URL, and APP_WEB_URL.

  3. The request routing details for your Dify instance. Is there any intermediate reverse proxy? If so, how does it handle requests?

@QuantumGhost commented on GitHub (Feb 14, 2026): @HZJprince It seems like this is a deployment-related issue. To facilitate the debugging process, could you please provide the following information? 1. Network request logs and browser console logs for the form page. You can collect the network logs using the following steps: a. Open the Chrome Developer Tools. b. Paste the link received in the email and navigate to the form page. c. Export the requests using the `Export HAR (sanitized)` feature, as shown in the image below: <img width="764" height="151" alt="Image" src="https://github.com/user-attachments/assets/3af62bf9-e34f-4eff-abee-4315e2624afc" /> 2. The configuration values for `CONSOLE_API_URL`, `CONSOLE_WEB_URL`, and `APP_WEB_URL`. 3. The request routing details for your Dify instance. Is there any intermediate reverse proxy? If so, how does it handle requests?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#22216