Widget Blueprint breakpoints hit during a Tick event do not engage the debugger.

The user comment on the Salesforce issue " This is a regression from the behaviour in 5.3.X, and I've reproduced it in 5.4.0, 5.4.1, and 5.4.2. The specific issue/change that caused this regression is in [Link Removed]. The fix applied in this issue does prevent the editor from deadlocking/crashing when the wrong viewport is active when a breakpoint is encountered, but it breaks the actual widget debugging functionality."

1. Create a Widget Blueprint.
2. In the created Blueprint add "Event Tick" and connect it with "Print Text".
3. Add a breakpoint to the "Event Tick".
4. Add the previously created widget to the level blueprint.
5. Connect the widget in the level blueprint with "Event Play" and "Add to Viewport".
6. Start PIE session.

Actual Result: The PIE session pauses and the blueprint debugger does not engage. The error notification pops up in the right bottom of the screen with "Debugging Mode Fail/The window is ticking" and the user cannot do anything unless exiting the PIE.

Expected Result: The blueprint debugger engages at the encountered breakpoint.