# CRITICAL BUG: Race condition between Native Forms, Choice Components, and Row Owners causes silent data loss (bypassing 'Required' flag) **URL:** \ **Category:** Report a Bug\ **Created:** [August 4, 2026, 4:26pm UTC](https://community.glideapps.com/t/critical-bug-race-condition-between-native-forms-choice-components-and-row-owners-causes-silent-data-loss-bypassing-required-flag/87539 "2026-08-04T16:26:10Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [August 8, 2026, 11:29pm UTC](https://community.glideapps.com/t/critical-bug-race-condition-between-native-forms-choice-components-and-row-owners-causes-silent-data-loss-bypassing-required-flag/87539/6 "2026-08-08T23:29:19Z")
This is a known and documented security restriction to prevent backdoor access to unowned data. Your original question mentioned an issue with assigning a Row Owner column with a role value. There was no mention of assigning a Role column with a role value. Two very different scenarios that I could have clarified very quickly if you had answered the questions in my first reply. In any case, a role can only be assign via client side actions or workflows if the user setting the role possess the same role during row creation. If a user does not possess the same role themselves, or the row has already been created, then the role can only be set via a server side workflow or directly through the data editor. There are several posts that cover this. --- _[View the full topic](https://community.glideapps.com/t/critical-bug-race-condition-between-native-forms-choice-components-and-row-owners-causes-silent-data-loss-bypassing-required-flag/87539)._