# Critical Onboarding Navigation Bug - UI Unresponsive to Actions Despite All Known Workarounds **URL:** \ **Category:** General\ **Created:** [July 30, 2025, 9:22am UTC](https://community.glideapps.com/t/critical-onboarding-navigation-bug-ui-unresponsive-to-actions-despite-all-known-workarounds/83546 "2025-07-30T09:22:38Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![VeeduWay](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/veeduway/32/89191_2.png) [@VeeduWay](https://community.glideapps.com/u/VeeduWay)\ **Post date:** [July 30, 2025, 9:22am UTC](https://community.glideapps.com/t/critical-onboarding-navigation-bug-ui-unresponsive-to-actions-despite-all-known-workarounds/83546/1 "2025-07-30T09:22:38Z")
### **Bug Report Summary for Glide Support** **Project Name:** VeeduWay **Subject: Critical Onboarding Navigation Bug - UI Unresponsive to Actions Despite All Known Workarounds** **Description:** My app’s new user onboarding flow is completely blocked. When a user clicks a button on the “Welcome Screen” to select their role, the app remains stuck on the Welcome Screen and fails to navigate to the next step. **Critical Findings:** - The `Set Column Values` action in the workflow **is working perfectly**. We have confirmed every time that the user’s `Role` is being correctly written and saved in the `Users` table in the Data Editor. - The core issue is that the app’s User Interface **is not reacting to this data change**. Neither visibility rules nor direct `Go to tab` actions are executing after the data is successfully updated. **Exhaustive List of Failed Troubleshooting Steps:** We have methodically diagnosed and attempted to fix this issue with every known method, none of which have worked: 1. **Verified Core Logic:** Confirmed all visibility rules, data table structures, and action configurations are set up correctly per Glide documentation. 2. **Confirmed User Context:** All tests were performed while “Viewing as” a specific, signed-in user with an initially empty `Role`. 3. **Checked for Nuance:** Ruled out case-sensitivity issues and confirmed the `Role` column is not “user-specific.” 4. **Isolated Variables:** Changed the `Go to tab` destination to different screens; the navigation failed regardless of the target. 5. **Rebuilt from Scratch:** The entire `Welcome Screen` and its components were deleted and rebuilt from a clean slate. The issue persisted identically. 6. **Implemented Community Workaround #1:** An intermediate `Wait` action (1 second) was added between setting the role and navigating. This did not solve the issue. 7. **Implemented Community Workaround #2:** An advanced “Intermediate Screen” pattern was fully implemented to force a data/UI sync. The navigation from the Welcome Screen to the Intermediate Screen still failed. ---
**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:** [July 30, 2025, 9:25am UTC](https://community.glideapps.com/t/critical-onboarding-navigation-bug-ui-unresponsive-to-actions-despite-all-known-workarounds/83546/2 "2025-07-30T09:25:42Z")
> [@VeeduWay](#): > > The `Set Column Values` action in the workflow **is working perfectly**. We have confirmed every time that the user’s `Role` is being correctly written and saved in the `Users` table in the Data Editor. That’s your problem. Glide does not allow you to set a users role through a user initiated action. You must either use a server side workflow, or use the Glide API. Whilst it might appear that the change is being made, the change will be reversed as soon as the App syncs with the Glide back end. This is expected and documented behaviour. ---
**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\ **Post date:** [August 6, 2025, 9:26am UTC](https://community.glideapps.com/t/critical-onboarding-navigation-bug-ui-unresponsive-to-actions-despite-all-known-workarounds/83546/3 "2025-08-06T09:26:12Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.