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

Timer script execution error. #12349

New Issue
Closed
opened 2026-02-21 19:07:01 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:07:01 -05:00
Owner
Copy Link
Copy Source

Originally created by @IAMJOYBO on GitHub (Mar 30, 2025).

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

v1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Image

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @IAMJOYBO on GitHub (Mar 30, 2025). ### 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 v1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/7be642f3-b513-477a-a764-fccf78545fe8) ![Image](https://github.com/user-attachments/assets/b4247707-9378-4b0a-8614-ae26e7cd1dbe) ![Image](https://github.com/user-attachments/assets/ca81b30a-8e2f-4a23-a10e-4c0e7cd45a8d) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:07:01 -05:00
yindo closed this issue 2026-02-21 19:07:01 -05:00
yindo commented 2026-02-21 19:07:01 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 30, 2025):

The "ERR_MODULE_NOT_FOUND" error for the 'axios' package in your Dify scheduled workflow suggests that the module is not being found during execution, despite being installed. Here are some steps to troubleshoot and resolve this issue:

  1. Verify Installation Path: Ensure that the 'axios' package is installed in the correct directory where the Node.js script is being executed. The package should be in the node_modules directory relative to your script.

  2. Check Node.js Version Compatibility: Make sure that the version of Node.js you are using (v22.13.1) is compatible with the version of 'axios' (1.4.8). Although this is unlikely to be the issue, it's worth verifying.

  3. Environment Variables: Check if there are any environment variables or path settings in the QingLong panel that might affect module resolution. Ensure that the NODE_PATH environment variable, if set, includes the path to the node_modules directory.

  4. Reinstall Dependencies: Sometimes, reinstalling the dependencies can resolve module resolution issues. You can try removing the node_modules directory and the package-lock.json file, then run npm install again.

  5. Script Execution Context: Ensure that the script is being executed in the correct context where the dependencies are available. If the script is being run from a different directory, it might not have access to the installed modules.

  6. QingLong Configuration: Double-check the QingLong panel's configuration for any settings that might affect how Node.js scripts are executed, such as custom execution paths or isolated environments.

If these steps do not resolve the issue, consider checking the QingLong panel's documentation or support resources for any specific configurations related to Node.js module resolution.

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Mar 30, 2025): <!-- Answer --> The "ERR_MODULE_NOT_FOUND" error for the 'axios' package in your Dify scheduled workflow suggests that the module is not being found during execution, despite being installed. Here are some steps to troubleshoot and resolve this issue: 1. **Verify Installation Path**: Ensure that the 'axios' package is installed in the correct directory where the Node.js script is being executed. The package should be in the `node_modules` directory relative to your script. 2. **Check Node.js Version Compatibility**: Make sure that the version of Node.js you are using (v22.13.1) is compatible with the version of 'axios' (1.4.8). Although this is unlikely to be the issue, it's worth verifying. 3. **Environment Variables**: Check if there are any environment variables or path settings in the QingLong panel that might affect module resolution. Ensure that the `NODE_PATH` environment variable, if set, includes the path to the `node_modules` directory. 4. **Reinstall Dependencies**: Sometimes, reinstalling the dependencies can resolve module resolution issues. You can try removing the `node_modules` directory and the `package-lock.json` file, then run `npm install` again. 5. **Script Execution Context**: Ensure that the script is being executed in the correct context where the dependencies are available. If the script is being run from a different directory, it might not have access to the installed modules. 6. **QingLong Configuration**: Double-check the QingLong panel's configuration for any settings that might affect how Node.js scripts are executed, such as custom execution paths or isolated environments. If these steps do not resolve the issue, consider checking the QingLong panel's documentation or support resources for any specific configurations related to Node.js module resolution. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/bdf1b972-f17d-4565-b6c9-aefb4ac24b0f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/bdf1b972-f17d-4565-b6c9-aefb4ac24b0f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/bdf1b972-f17d-4565-b6c9-aefb4ac24b0f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/bdf1b972-f17d-4565-b6c9-aefb4ac24b0f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/bdf1b972-f17d-4565-b6c9-aefb4ac24b0f?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/bdf1b972-f17d-4565-b6c9-aefb4ac24b0f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/bdf1b972-f17d-4565-b6c9-aefb4ac24b0f?feedback_type=other)</sup>
yindo commented 2026-02-21 19:07:01 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 30, 2025):

This isn't related to dify itself.

@crazywoola commented on GitHub (Mar 30, 2025): This isn't related to dify itself.
yindo commented 2026-02-21 19:07:02 -05:00
Author
Owner
Copy Link
Copy Source

@zhangdahai112 commented on GitHub (Apr 15, 2025):

Image
follow my steps it works

@zhangdahai112 commented on GitHub (Apr 15, 2025): ![Image](https://github.com/user-attachments/assets/bee8694a-c298-44fd-adda-9b6f29c1158d) follow my steps it works
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#12349
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?