Hello Glide Community!
We’re developing Monster AI Languages on Glide’s Explorer plan, using native Glide Tables.
Our application’s Users table is also its User Profiles table, so migrating that table to Big Tables is not an appropriate solution.
We have an existing server-side webhook-triggered workflow that:
1. Receives an HTTPS POST from our Google Cloud Run service.
2. Extracts a specific User_Row_ID and three administrative field values using Query JSON.
3. Queries the native Users table for the exact User_Row_ID.
4. Executes Set Column Values against the matching Users row.
This generally works, but we need to reliably verify that all three values were actually persisted to the intended Users row, rather than simply treating HTTP webhook acceptance as proof of success.
Our technical questions
1. Sequential Query consistency
If a webhook workflow executes:
Query → Set Column Values → Query
Does the second Query retrieve freshly persisted values, or might it reuse cached or previously evaluated results?
2. Write completion guarantees
Does Set Column Values complete its database persistence before the next server-side workflow action executes?
3. Independent verification workflow
Could we use a separate webhook-triggered, read-only workflow that queries the same Users row after the original write workflow has executed?
Would this second execution retrieve independently evaluated, current stored values? Are there known consistency delays?
4. Returning actual stored values
Could the second workflow use Trigger Webhook to send its Query results to our Cloud Run HTTPS endpoint, allowing our JavaScript to compare the returned Row ID and three actual stored values against the expected values?
5. Explorer-compatible production architecture
Glide’s AI support agent, Fin, advised that webhook-triggered workflows with non-Big Table sources may not provide reliable real-time read/write behavior, and that Big Tables are recommended for synchronous saves.
However, our Users table must remain the application’s native User Profiles table.
What is Glide’s recommended, supported mechanism for verifying successful updates to a native Users/User Profiles table on Explorer?
We are not seeking access to the external Glide Data API or an expensive plan upgrade.
We already use Google Cloud Run, Firestore, and Stripe for secure subscription administration. We want a reliable acknowledgment or reconciliation mechanism without introducing unnecessary architectural complexity.
If possible, we’d particularly appreciate clarification from a Glide staff member or engineer regarding the actual persistence and Query consistency guarantees.
Thank you for your guidance!
John Mastronardo
Developer, Monster AI Languages
Glide Explorer Plan
If a Glide staff member needs additional account or application details, I would be happy to provide them privately.