Disable message saving to DB via an environment variable #3837
+48
−3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
oh great if this PR is doing it's work it would solve #3832 ! |
|
one of the downside is that you won't be able to have source documents, files, images, tools etc displayed on the chat thats because we save all these items on the flowise database, and only the text message is saved to the 3rd party memory node |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add an environment variable
DISABLE_MESSAGE_SAVINGwhich disables messages being saved to the database. This is useful for scenarios where you are avoiding saving potential PII to your Flowise instance.This disables the buffer memory nodes. If they were used in a Flow it will no longer work and will instead show an error on run and in the UI. Because this is a very serious environment variable to enable, so I think this is an okay result.
Analytics integrations continue to work if enabled per flow.
Feedback will no longer work but I have not added error messages for that. I could add a validation to prevent Feedback being toggled on?
The messages UI will show a different error message:
Future upgrades to this may shift this from an environment variable to a per-flow setting but this is the simpler approach for now.
Please let me know if you would like any changes to this or there are any other potential areas impacted!
cc @tgmerritt @HenryHengZJ