App: AppSheet Core (Google Workspace), table “Hey reach leads,” data source Google Sheets.
Symptom: Editing a LongText field (and other fields) via the app’s Edit form and clicking Save shows the new value immediately in the app’s Detail view, updates the row’s ChangeTimestamp column, and correctly logs Old Value/New Value in our own Activity Log automation. However, the underlying Google Sheet cell is never actually updated - confirmed by direct inspection of the sheet (Ctrl+F for the saved text returns 0 matches).
What I’ve ruled out:
- Schema/column-position desync (ran Regenerate Structure, no change)
-
- Data validation rules on the column (none exist)
-
- Protected ranges/sheets (none exist)
-
- Table set to read-only (Updates/Adds/Deletes all enabled)
-
- Duplicate key values causing a wrong-row match (confirmed unique key)
-
- Phantom/duplicate appended rows from a failed key match (none found)
-
- A regular filter (Data > Create a filter) on the sheet, removed it per the known Google Sheets bug noted in your own docs (App changes are not captured in the spreadsheet or the app), did NOT resolve the issue
-
- Manual edits made directly in Google Sheets work fine and save correctly, this is specific to writes coming from the AppSheet app
- Evidence from the Enterprise Audit Log (Manage > Monitor > Launch log analyzer)
- Operation: Edit row, Table: Hey reach leads -
- RequestId: 596696, Timestamp: 2026-07-15T14:24:42Z
-
- Result: Success
-
- Source Id in table settings confirmed correct, matches the actual spreadsheet DocId and worksheet name
- This looks like a genuine disconnect between AppSheet’s internal state (which believes the write succeeded) and the actual Sheets API write, since the audit log reports success for a write that never happened. Has anyone seen this, or is there a way to get engineering to trace RequestId 596696 server-side?
