You might check the Database to make sure your user is actually that user type. I made a mistake in my own app where I forgot to make my user the right type, and ran into a similar issue. I’d check there first, sometimes the easiest things are the problem!
Possibly because the “page has loaded event” triggers before the data is being pulled, so current user field shows a value of empty at the time of the action.
Possible workarounds: (untested)
Add a condition on the data to the event: When page is loaded, AND when current user’s type is “wrongtypeforthispage”. Possibly the condition doesn’t need to be the same as the one on the action.
Add a pause before the action where you conditionally navigate to another page.
@mishav - #1 solved the issue. The conditional must be on the event, rather than the action (I have no condition on the action and works as intended).
I actually had some pages like this, most the condition was on the action - which is why I thought there was an issue between live and dev - not the case though, nothing to do with live or dev.
Everything working as it should on live and dev now…thank you for your help.