Azure AD B2C - UserFlow/Custom Policy Restarting

Scott-7702 21 Reputation points
2022-09-20T19:55:04.037+00:00

Adding our use case.

The following sequence of actions will result in the user journey being restarted and, as a result, returns unexpected behavior:

  1. Open the Sign-Up policy flow.
  2. In a new tab, open the Sign-In flow.
  3. Fill out the initial page of the Sign-Up flow and click submit
  4. At this point the user journey will restart and results in unexpected behavior. In the AI logs we see:
    • Web.TPEngine.StateMachineHandlers.JourneyRestartHandler
    • [{"Key":"RestartingJourney","Value":"Current orchestration step set to 0"}]

This appears to be a known B2C issue according to:

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
35,519 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. 2022-09-28T20:08:59.58+00:00

    Hello @Scott-7702 and thanks for reaching out. It's recommended to avoid running the same Azure AD B2C user flow in multiple tabs since the flow current orchestration step and progress state is shared between all tabs opened for the same, thus any progress or change made on one tab will update the state for the other ones.

    This is by design and currently there are no plans to change this.

    Let us know if you need additional assistance. If the answer was helpful, please accept it and complete the quality survey so that others can find a solution.