I have a rare but reoccurring problem, where during my app’s sign up process (which is 4 pages), a user will pause on say page 2 but keep the tab open. When they come back to it days later, they’re logged out but I guess the page doesn’t refresh automatically so my action “Do When Current User Is Logged Out → go to page home” doesn’t work.
How do I force the user out of the page if they’re logged out and the browser doesn’t refresh to run the action to send then home?
Sent you a message
Let me make it simpler. Let’s say you have two windows of the same page with the same user. I go to one window and log out - that action takes me home. I look at the other window - technically the user is logged out but all buttons are still clickable and the page didn’t refresh so the user is not sent home.
I tried Do when user logged out → go home, do every 3 seconds when user logged out → go home. Can’t get the page to do anything
If your privacy rules are setup correctly no data can be manipulated in either of these scenarios.
If it’s a single page app using states to navigate they can still navigate but new data won’t be pulled bc the server will reject it. If you use paths/go to page to navigate (even on single page apps using go to page) it will pickup the edge cases you’re referring to.
They will have to actually refresh for that to be over ridden and in this case it’ll redirect back to home.
You’re correct, the way I have it the data isn’t manipulated, however I really don’t want them to be able to click the buttons. Especially the last one which, even though logged out, still takes them to a page that I really don’t want them to go to.
Despite me adding the “only if user logged in” action to the workflow of these buttons, it doesn’t work
Put some sort of blocker for logged out users on the page you don’t want people to access.
This topic was automatically closed after 70 days. New replies are no longer allowed.
