I have discovered a defect in the OutSystems UI mobile lifecycle regarding the interaction between Bottom Sheet navigation and the PullToRefresh pattern.

If a user navigates away from a screen while a Bottom Sheet is still open (without explicitly closing it first via logic), the CSS classes responsible for locking the body scroll are not removed from the  tag.

When the user subsequently navigates to a screen that uses PullToRefresh (either by navigating back or navigating to the same screen), the feature fails to trigger. This happens because the  element still retains the class osui-bottom-sheet--is-active, which forces overflow: hidden on the window, tricking the PullToRefresh widget into thinking scrolling is locked.