Issue with "Current user is logged out" workflow

I have a “when condition is true” set to “everytime” that is set to trigger when “Current is logged out”, the action being to redirect them back to the index/login page.

However, this does not seem to be triggering properly - the user is logged out (as other details on the page that refer to current user come up blank, as they should) but the redirect doesn’t happen. Its a simple “Go to page” navigation.

So wondering if there is some flaw in the “Current user is logged in” status not being registered properly?

Can you share a screenshot of your workflow? Have you put a text on the page that uses ‘Current user’s logged out’ and see if that returns yes or no?

How do you trigger your logout command.? check workflow and arrange properly, navigation should be the last command on your workflow. on your navigation workflow set condition “only when current user is logged out”.

There’s two instances where it should carry this out.

The first being as a result of “detect user has become inactive”

r

The current user is being logged out, because in the dashboard I have a “Currently logged in as First name/last name/ email”, which displays blank when this happens. So thinking about it further, the issue here seems to be the “go to page” action.

As a failsafe I tried putting a straightforward “When current user is logged out”, such that if for some reason the above workflow doesn’t do the trick, the other should fire anyway. but again, no redirect.

In addition this seems to be sporadic - most of the time it works, but every now and then it doesn’t, which leaves end users confused when they are logged out but still within the dashboard (and clicking logout does nothing, even though the actions are “log the user out” and then again, go to index).

Its just odd…primarily because there’s nothing deep or complex going on here.

you can create a state or set a condition for the navigation

create a yes/no state . set the default value to no. set state to your logout button.
then your condition is "when state is yes, navigate to "

I mean, I can try that…but really shouldn’t have to since that is what is already supposed to be happening via the existing workflows.

yeah you are right , can you share the app with me if you dont mind

or can you create another navigation workflow to a separate page because from my experience, your work flow arrangement may also affect your result

This topic was automatically closed after 14 days. New replies are no longer allowed.