# Send user to top of screen with action **URL:** \ **Category:** Ask for Help\ **Created:** [December 7, 2020, 7:38am UTC](https://community.glideapps.com/t/send-user-to-top-of-screen-with-action/19483 "2020-12-07T07:38:53Z")\ **Posts on this page:** 1\ **Showing post:** 24
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [December 10, 2020, 4:31am UTC](https://community.glideapps.com/t/send-user-to-top-of-screen-with-action/19483/24 "2020-12-10T04:31:07Z")
Functionally, I think it works fine. But there seems to be some sort of race condition going on with the action sequence that ends up creating a very confusing user experience. It’s almost like the toggle is being flipped multiple times (it isn’t) and so the screen switches between the two states 2 or 3 times before finally settling down. I’m not exactly sure what is going on, which is why I posted that [other question](https://community.glideapps.com/t/action-sequencing-blocking-or-non-blocking/19601). It could be because some actions are being fired before a previous action is completed, or maybe it’s a data sync issue with several actions firing one after the other. But without knowing what the expected behaviour should be, that’s just wild speculation. This is a fairly extreme example (with 70+ components on the screen, all being toggled on/off rapidly), but I’ve also observed similar behaviour with just a handful of components. --- _[View the full topic](https://community.glideapps.com/t/send-user-to-top-of-screen-with-action/19483)._