langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Add finish_reason to the Bedrock plugin #268

New Issue
Closed
opened 2026-02-16 10:18:41 -05:00 by yindo · 10 comments
yindo commented 2026-02-16 10:18:41 -05:00
Owner
Copy Link
Copy Source

Originally created by @yosse95ai on GitHub (May 9, 2025).

Self Checks

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

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I want to use a loop node to repeat the generation of text as long as the finish_reason is max_token, but the output of the Bedrock plugin does not include the finish_reason. The only output I can receive at the next node is text.

Image

2. Additional context or comments

My Bedrock plugin is v0.0.17 now.
On the other hand, the Claude 3.5 Sonnet output itself contains a finish_reason. We need a way to reference this in the next node.

Image

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @yosse95ai on GitHub (May 9, 2025). ### Self Checks - [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. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. I want to use a loop node to repeat the generation of text as long as the finish_reason is max_token, but the output of the Bedrock plugin does not include the finish_reason. The only output I can receive at the next node is text. <img width="554" height="528" alt="Image" src="https://github.com/user-attachments/assets/c05f1e36-949b-48e6-acdb-34e8bcc6043f" /> ### 2. Additional context or comments My Bedrock plugin is `v0.0.17` now. On the other hand, the Claude 3.5 Sonnet output itself contains a finish_reason. We need a way to reference this in the next node. <img width="390" alt="Image" src="https://github.com/user-attachments/assets/ebc289a1-7370-457e-80f0-f02c99481697" /> ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo closed this issue 2026-02-16 10:18:41 -05:00
yindo commented 2026-02-16 10:18:43 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (May 10, 2025):

What's your plugin version?

@crazywoola commented on GitHub (May 10, 2025): What's your plugin version?
yindo commented 2026-02-16 10:18:43 -05:00
Author
Owner
Copy Link
Copy Source

@yosse95ai commented on GitHub (May 12, 2025):

@crazywoola
Thank you for your response.
My Bedrock plugin is v0.0.17 now.

Image

And my Dify version is v1.3.1 now.

@yosse95ai commented on GitHub (May 12, 2025): @crazywoola Thank you for your response. My Bedrock plugin is v0.0.17 now. ![Image](https://github.com/user-attachments/assets/933e5855-db29-498c-9fab-659e718fbb2f) And my Dify version is v1.3.1 now.
yindo commented 2026-02-16 10:18:43 -05:00
Author
Owner
Copy Link
Copy Source

@yosse95ai commented on GitHub (Jun 12, 2025):

@crazywoola
Is there any news?

@yosse95ai commented on GitHub (Jun 12, 2025): @crazywoola Is there any news?
yindo commented 2026-02-16 10:18:43 -05:00
Author
Owner
Copy Link
Copy Source

@yadanchina commented on GitHub (Jul 2, 2025):

Now, due to the reason of finic_reason, it is necessary to obtain finic_reason, but the LLM node does not provide a return

@yadanchina commented on GitHub (Jul 2, 2025): Now, due to the reason of finic_reason, it is necessary to obtain finic_reason, but the LLM node does not provide a return
yindo commented 2026-02-16 10:18:43 -05:00
Author
Owner
Copy Link
Copy Source

@yosse95ai commented on GitHub (Jul 23, 2025):

Is there any news?

@yosse95ai commented on GitHub (Jul 23, 2025): Is there any news?
yindo commented 2026-02-16 10:18:44 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 7, 2025):

No news. for this one. Afaik.

@crazywoola commented on GitHub (Aug 7, 2025): No news. for this one. Afaik.
yindo commented 2026-02-16 10:18:45 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 24, 2025):

Hi, @yosse95ai. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested adding the "finish_reason" field to the Bedrock plugin output to control looping behavior.
  • This feature is similar to what other plugins like Claude 3.5 Sonnet provide.
  • You are using Bedrock plugin v0.0.17 and Dify v1.3.1.
  • Another user also expressed the need for this feature since the LLM node lacks "finish_reason."
  • A maintainer confirmed there is no update on this request yet.

Next Steps:

  • Please let me know if this feature is still relevant to the latest version of the dify-official-plugins repository by commenting on this issue.
  • If I do not hear back within 5 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 24, 2025): Hi, @yosse95ai. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested adding the "finish_reason" field to the Bedrock plugin output to control looping behavior. - This feature is similar to what other plugins like Claude 3.5 Sonnet provide. - You are using Bedrock plugin v0.0.17 and Dify v1.3.1. - Another user also expressed the need for this feature since the LLM node lacks "finish_reason." - A maintainer confirmed there is no update on this request yet. **Next Steps:** - Please let me know if this feature is still relevant to the latest version of the dify-official-plugins repository by commenting on this issue. - If I do not hear back within 5 days, I will automatically close this issue. Thank you for your understanding and contribution!
yindo commented 2026-02-16 10:18:45 -05:00
Author
Owner
Copy Link
Copy Source

@yosse95ai commented on GitHub (Sep 2, 2025):

I am planning to solve this issue. Currently, I am reading the documentation for contributing and performing code reading.

@yosse95ai commented on GitHub (Sep 2, 2025): I am planning to solve this issue. Currently, I am reading the documentation for contributing and performing code reading.
yindo commented 2026-02-16 10:18:45 -05:00
Author
Owner
Copy Link
Copy Source

@yosse95ai commented on GitHub (Sep 7, 2025):

I cannot resolve this issue...

@yosse95ai commented on GitHub (Sep 7, 2025): I cannot resolve this issue...
yindo commented 2026-02-16 10:18:45 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 7, 2025):

@crazywoola The user yosse95ai mentioned they cannot resolve the issue that was previously marked stale and closed; could you please assist them with this?

@dosubot[bot] commented on GitHub (Sep 7, 2025): @crazywoola The user yosse95ai mentioned they cannot resolve the issue that was previously marked stale and closed; could you please assist them with this?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label
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-official-plugins#268
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?