# Human-readable Row ID **URL:** \ **Category:** Community Resources\ **Created:** [May 4, 2025, 4:46pm UTC](https://community.glideapps.com/t/human-readable-row-id/81703 "2025-05-04T16:46:17Z")\ **Posts on this page:** 1\ **Showing post:** 9
**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:** [May 5, 2025, 3:29am UTC](https://community.glideapps.com/t/human-readable-row-id/81703/9 "2025-05-05T03:29:28Z")
I know it doesn’t. Glide actions such as Add Row and Increment are not atomic, and never have been. At least not with user initiated actions. Server-side workflows are relatively new, but from what I’ve seen so far I believe that they could be subject to the same concurrency issues. > [@new\_button Updates to the Glide + Make integration](https://community.glideapps.com/t/updates-to-the-glide-make-integration/67979/16): > > Increment is not an atomic operation. The increment happens on the client, and the result is sent to the server. For atomic increment, you should use Call API with a service like Upstash that offers serverless redis (a database with first-class support for atomic increment). You can get a good result this way! We did it for PGA when they needed a distributed counter for their grandstands. We’d like to offer atomic increment in Glide but it’s not a top request from customers yet. --- _[View the full topic](https://community.glideapps.com/t/human-readable-row-id/81703)._