langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 12:36:14 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Extract web content with Firecrawl cannot set Max depth to 0 #5277

New Issue
Closed
opened 2026-02-21 18:10:14 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:10:14 -05:00
Owner
Copy Link
Copy Source

Originally created by @AAEE86 on GitHub (Aug 28, 2024).

Originally assigned to: @iamjoel, @YIXIAO0 on GitHub.

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

0.7.2

Cloud or Self Hosted

Cloud, Self Hosted (Docker)

Steps to reproduce

Quicker_20240828_163534

✔️ Expected Behavior

set Max depth to 0

❌ Actual Behavior

cannot set Max depth to 0

Originally created by @AAEE86 on GitHub (Aug 28, 2024). Originally assigned to: @iamjoel, @YIXIAO0 on GitHub. ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.7.2 ### Cloud or Self Hosted Cloud, Self Hosted (Docker) ### Steps to reproduce ![Quicker_20240828_163534](https://github.com/user-attachments/assets/1f1fe2bb-3980-44e8-8c36-cf91df572967) ### ✔️ Expected Behavior set Max depth to 0 ### ❌ Actual Behavior cannot set Max depth to 0
yindo added the 🐞 bug label 2026-02-21 18:10:14 -05:00
yindo closed this issue 2026-02-21 18:10:14 -05:00
yindo commented 2026-02-21 18:10:14 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 28, 2024):

You can't set the Max depth to 0 when extracting web content with Firecrawl in Dify version 0.7.2 because the tooltip for the Max depth option specifies that depth 0 just scrapes the page of the entered URL. Therefore, setting the Max depth to 0 is a valid configuration and should be allowed.

If you are experiencing issues setting the Max depth to 0, it might be due to a bug or a misconfiguration in the application. Additionally, ensure that Firecrawl is properly configured with the API key, as indicated in the Dify documentation.

There is validation logic in the Firecrawl tool's code that might prevent setting the Max depth to 0. Specifically, in the handleRun function, the max_depth option is deleted if it is an empty string. However, there is no explicit check for a value of 0, so setting max_depth to 0 should not be prevented by this specific piece of validation logic [1][2].

If you are unable to set the Max depth to 0, it is likely a bug or a configuration issue that needs to be addressed.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Aug 28, 2024): <!-- Answer --> You can't set the Max depth to 0 when extracting web content with Firecrawl in Dify version 0.7.2 because the tooltip for the Max depth option specifies that depth 0 just scrapes the page of the entered URL. Therefore, setting the Max depth to 0 is a valid configuration and should be allowed. If you are experiencing issues setting the Max depth to 0, it might be due to a bug or a misconfiguration in the application. Additionally, ensure that Firecrawl is properly configured with the API key, as indicated in the Dify documentation. There is validation logic in the Firecrawl tool's code that might prevent setting the Max depth to 0. Specifically, in the `handleRun` function, the `max_depth` option is deleted if it is an empty string. However, there is no explicit check for a value of 0, so setting `max_depth` to 0 should not be prevented by this specific piece of validation logic <sup>[[1]](https://github.com/langgenius/dify/blob/main/web/app/components/datasets/create/website/firecrawl/index.tsx)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/firecrawl/tools/crawl.py)</sup>. If you are unable to set the Max depth to 0, it is likely a bug or a configuration issue that needs to be addressed. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#5277
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?