I’m facing issues with my Dash web app which has a key write back functionality as the point of the app is for people to provide feedback on certain data. I’ve noticed that when I’m testing it myself, the data writes back perfectly. However, when there are multiple users with active sessions at the same time and click the submit button, the data doesn’t get captured and sent back to my snowflake backend. Any tips on what to do?
HI @plotly2,
welcome to the community!
I am not used to snowflake and without a MRE it’s hard to say. But what kind of Session storage are you using - flask session with a redis backend?
Kind regards
1 Like
Hello @plotly2,
Welcome to the community!
I’d make sure that you are using key identifiers on your records to update the info, vs performing sweeping updates to mass amounts of data.
I personally keep a change log on grids used for user input.
Generally speaking it’s good practice to keep your Dash apps stateless. Introducing state can lead to a host of problems managing that state. Tools like persistence in Dash are helpful to make it easier to manage session state, and easier to deal with than backend storage like redid (as @Datenschubse mentions).
Because you’re using write back, you also might run into issues with database locks causing problems for you. Something worth looking into to help out with your architecture design here.
In Dash Enterprise, we offer Dash Enterprise Auth which gives you data and information about logged-in users, which makes it easier to associate actions with a specific user. More here: No-Code Authentication