# Row Numbers **URL:** \ **Category:** Ask for Help\ **Created:** [June 4, 2021, 7:02am UTC](https://community.glideapps.com/t/row-numbers/27619 "2021-06-04T07:02:51Z")\ **Posts on this page:** 1\ **Showing post:** 5
**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:** [June 4, 2021, 8:19am UTC](https://community.glideapps.com/t/row-numbers/27619/5 "2021-06-04T08:19:31Z")
Unfortunately, no. At least not if you’re only using Glide tables. There was a bit of excitement when the API Column was released into staging a few months ago, but that appears to have been shelved. If you’re using GSheets, then there are tricks that can be employed to address race conditions. This is something I’ve had to deal with recently, and I described the approach we took here ⬇ > [@clock3 System/GMT Time - Solved!](https://community.glideapps.com/t/system-gmt-time-solved/27524/17): > > mmm, in our case the issue isn’t so much not knowing each users relative time, but more about dealing with the fact that we can have multiple users all trying to do the same thing at the same time, and because of sync delays they end up tripping over each other. For example, record X becomes up for grabs, and 3 users all try to claim it at the same time. Because the initial change is local to each users device, it appears to each one that they’ve claimed X, and so they move on to the next step… Essentially, we did as you suggested, which was to use an intermediary (in this case, Integromat) as an indirect arbitrator. --- _[View the full topic](https://community.glideapps.com/t/row-numbers/27619)._