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

When selecting the JSON format for the SQL Execute plugin, the next step cannot select JSON #12305

New Issue
Closed
opened 2026-02-21 19:06:49 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:06:49 -05:00
Owner
Copy Link
Copy Source

Originally created by @huangguifeng on GitHub (Mar 28, 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

1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image When selecting the JSON format for the SQL Execute plugin, the next step cannot select JSON

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @huangguifeng on GitHub (Mar 28, 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 1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/35ef83f7-ec86-4729-a5dd-c49ccdc4e6a0) When selecting the JSON format for the SQL Execute plugin, the next step cannot select JSON ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:06:49 -05:00
yindo closed this issue 2026-02-21 19:06:49 -05:00
yindo commented 2026-02-21 19:06:49 -05:00
Author
Owner
Copy Link
Copy Source

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

To address the issue where the next step cannot select JSON output from the SQL Execute plugin, ensure that the JSON output is correctly configured. You can use the create_json_message method to format the output as JSON. This method takes a dictionary as input and outputs it as a JSON message. Additionally, make sure that the tool's output schema is defined in json_schema format to specify the structure of the JSON data that will be output [1].

If the issue persists, verify that the JSON output is correctly recognized by the subsequent steps in the workflow. This might involve checking the configuration settings or parameters in the workflow editor that affect JSON output selection.

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 28, 2025): <!-- Answer --> To address the issue where the next step cannot select JSON output from the SQL Execute plugin, ensure that the JSON output is correctly configured. You can use the `create_json_message` method to format the output as JSON. This method takes a dictionary as input and outputs it as a JSON message. Additionally, make sure that the tool's output schema is defined in `json_schema` format to specify the structure of the JSON data that will be output <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/jp/plugins/schema-definition/tool.md)</sup>. If the issue persists, verify that the JSON output is correctly recognized by the subsequent steps in the workflow. This might involve checking the configuration settings or parameters in the workflow editor that affect JSON output selection. <!-- 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/54a69f92-7b60-4915-8eee-aa35ae45ea3d?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/54a69f92-7b60-4915-8eee-aa35ae45ea3d?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/54a69f92-7b60-4915-8eee-aa35ae45ea3d?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/54a69f92-7b60-4915-8eee-aa35ae45ea3d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/54a69f92-7b60-4915-8eee-aa35ae45ea3d?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/54a69f92-7b60-4915-8eee-aa35ae45ea3d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/54a69f92-7b60-4915-8eee-aa35ae45ea3d?feedback_type=other)</sup>
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#12305
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?