You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The Rate Limiting settings in Chatflow Configuration are not being saved correctly. After configuring and saving the Rate Limiting settings, switching to another tab and then returning to the Rate Limiting tab shows that the settings have not been retained.
To Reproduce
Steps to reproduce the behavior:
Go to 'Chatflow Configuration'
Click on 'Rate Limiting' tab
Enable Rate Limiting and configure settings
Click 'Save' button
Switch to another tab in Chatflow Configuration
Return to the 'Rate Limiting' tab
Observe that the settings are not retained and Rate Limiting is shown as Disabled
Expected behavior
After saving the Rate Limiting settings and returning to the tab, the previously configured settings should be displayed and Rate Limiting should remain Enabled.
Screenshots
Rate.Limiting.mp4
Setup
Installation: Docker
Flowise Version: 2.1.2
OS: Ubuntu 22.04
Browser: Chrome
The text was updated successfully, but these errors were encountered:
Thank you for your response. However, I noticed that PR #3311 (merged on Oct 5) is already included in Flowise 2.1.2 change log (released on Oct 10), which is the version where I'm experiencing this issue.
Could you help verify if the fix in PR #3311 fully addresses the Rate Limiting persistence problem?
I'm still observing the following behavior in version 2.1.2:
Describe the bug
The Rate Limiting settings in Chatflow Configuration are not being saved correctly. After configuring and saving the Rate Limiting settings, switching to another tab and then returning to the Rate Limiting tab shows that the settings have not been retained.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
After saving the Rate Limiting settings and returning to the tab, the previously configured settings should be displayed and Rate Limiting should remain Enabled.
Screenshots
Rate.Limiting.mp4
Setup
The text was updated successfully, but these errors were encountered: