Why can my workflow retrieve results in both the testing and logging interfaces, but not in the webURL interface. I am working on a workflow that concatenates iterative content and returns a string

[zyjfly]

Self Checks

• 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 (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Dify version

Why can my workflow retrieve results in both the testing and logging interfaces, but not in the webURL interface. I am working on a workflow that concatenates iterative content and returns a string

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Why can my workflow retrieve results in both the testing and logging interfaces, but not in the webURL interface. I am working on a workflow that concatenates iterative content and returns a string

✔️ Expected Behavior

Why can my workflow retrieve results in both the testing and logging interfaces, but not in the webURL interface. I am working on a workflow that concatenates iterative content and returns a string

❌ Actual Behavior

Why can my workflow retrieve results in both the testing and logging interfaces, but not in the webURL interface. I am working on a workflow that concatenates iterative content and returns a string

[dosubot[bot]]

Your issue—where your workflow retrieves results in the testing and logging interfaces but not in the webURL interface—matches a known pattern in Dify. This can occur if the web interface is not properly updating its state after workflow execution, even though the backend completes the task successfully.

A similar issue has been reported where the workflow log shows successful execution, but the web page fails to display the results. This may be related to the onWorkflowFinished callback not being triggered correctly, or errors being caught (and possibly hidden) by the StatusPanel component in the web interface. If this callback or error handler fails, the UI may not update to show your results, even though they exist in the logs and testing views. You can review this finding here.

The webURL interface uses components like FireCrawl and WaterCrawl to handle URL input, crawling, and error handling. These components validate URLs and manage errors if the URL is invalid or if the crawling task fails. If your workflow depends on these components, any error or unhandled state in their logic could prevent results from being displayed, even if the backend workflow completes as expected. You can see the relevant implementation details here and here.

Troubleshooting steps:

• Check your browser’s developer console for errors when running the workflow via the webURL interface.
• Review the server logs for any errors or warnings that occur during the workflow execution.
• If possible, verify that the onWorkflowFinished callback is being triggered and that the StatusPanel component is not suppressing errors.

If you can provide more details about what you see (e.g., error messages, blank screens, or partial results), it may help narrow down the cause. If the issue persists, it may require a closer look at the frontend code handling workflow completion and error states.

To continue talking to Dosu, mention @dosu-bot.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[zyjfly]