dify - 💡(How to fix) Fix Multiple extensions in the input field type will result in rejection if it's an API. [1 comments, 2 participants]

TL;DR

The issue can be potentially resolved by adjusting the file type configuration for the input field in the chat flow to support ".txt" extensions in stream mode.

Guidance

• Verify that the file type configuration is correctly set to "Other File Types" with ".json" and ".txt" extensions when calling the API in stream mode.
• Check if changing the file type to "Document" allows the API to work correctly with ".txt" files, but note that this may not support ".json" extensions.
• Investigate the difference in behavior between browser and API calls to identify potential inconsistencies in file handling.
• Test the API call with different file types and extensions to isolate the issue and confirm the expected behavior.

Example

No code snippet is provided as the issue does not contain explicit code references.

Notes

The issue seems to be related to the specific configuration of the input field and file types, and the behavior difference between browser and API calls. Further investigation is needed to determine the root cause.

Recommendation

Apply a workaround by adjusting the file type configuration to "Document" if it allows the API to work correctly with ".txt" files, but be aware that this may not support ".json" extensions.