[FeatureRequest] make the value CODE_MAX_STRING_LENGTH customizable at runtime for each workflow

Self Checks

[X] I have searched for existing issues search for existing issues, including closed ones.
[X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[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.

THE PROBLEM:
Currently the default limit for the result string from the ‘Code Block’ is ‘80000’ characters. A measly output limit of 80Kb is insufficient for most tasks. I generate documents of many megabytes regularly. Currently this is a huge limitation for Defy. Especially since this setting is regulated by an env variable, CODE_MAX_STRING_LENGTH, that require the application to be restarted to be changed.

PROPOSED SOLUTION:
To solve this issue you should make the value ‘CODE_MAX_STRING_LENGTH’ customizable at runtime for each workflow from the workflow settings. You can’t force the user to restart the application anytime. Not to mention the Cloud version of Dify that cannot be restarted by the users. Different workflows have different needs. This limit must be set by the user according to what kind of data he processes and according to the results of his tests. So the flexibility of a value editable at runtime for each workflow is a practical need.

2. Additional context or comments

No response

3. Can you help us with this feature?

[ ] I am interested in contributing to this feature.

Hi, @Emasoft. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

Feature request to make CODE_MAX_STRING_LENGTH customizable at runtime.
Current limit of 80,000 characters is insufficient for large document generation.
Changing the limit requires an application restart, problematic for cloud users.
Suggestion to adjust this setting within workflow settings.
No additional comments or activities on the issue.

Next Steps:

Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here.
If there is no response, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

langgenius / dify