Hey John, thanks for your sample flow. I think the issues with it arise as you check the OAuth token within an existing UserDialog. And you can't safely redirect to another page within that JSF Dialog without loosing context information. To work around for that problem: I think it would be easier to work with extra screens/Ui Dialogs in case the OAuth token is not present/valid. You could even stick to your current solution and leave the already running dialog with an ErrorEnd event that event, which you catch outside the dialog and if necessary delegate the request to the OAuth form UI. A solution very similar to my proposal can be found in the official 'ConnectivityDemos' that 'ConnectivityDemos', which are shipped as Designer sample. See Import -> Axon.ivy > Samples > ConnectivityDemos : ![alt text][1] [1]: https://answers.axonivy.com/upfiles/oauthConnectivityDemos.png

Hey John, thanks for your sample flow. I think the issues with it arise as you check the OAuth token within an existing UserDialog. And you can't safely redirect to another page within that JSF Dialog without loosing context information. To work around that problem: I think it be easier to work with extra screens/Ui Dialogs in case the OAuth token is not present/valid. You could even stick to your current solution and leave the already running dialog with an ErrorEnd event that you catch outside the dialog and if necessary delegate the request to the OAuth form UI. A solution very similar to my proposal can be found in the official 'ConnectivityDemos' that are shipped as Designer sample. See Import -> Axon.ivy > Samples > ConnectivityDemos : ![alt text][1] [1]: https://answers.axonivy.com/upfiles/oauthConnectivityDemos.png