Hi all,
Every Automation Bot in our app whose Process contains a “Call a webhook” (RUN_TASK) step has stopped executing entirely — not failing, but showing zero entries in Automation Monitor, as if the engine never attempts to run them. This affects 11 different Bots across 6+ unrelated tables, both old and recently-touched ones. Meanwhile, the one Bot in the app whose Process has no webhook step (only “Run actions on a set of rows”) continues to run perfectly, 100% completion rate.
It’s a regression, not a config that never worked. Our own backend (a Google Apps Script Web App that these webhooks call, which then writes to our Supabase DB) has real data proving the webhooks fired successfully from 2026-04-20 to 2026-06-11. Since 2026-06-11, nothing — even though the triggering field changes (e.g. an approval-status flip) keep happening normally every day.
What we’ve already ruled out (happy to share full details on request):
- Event
FilterConditionsyntax — fixed a bare-column-comparison bug on two Bots (switched to[_THISROW_BEFORE]/[_THISROW_AFTER]), matching the one working Bot’s style. Necessary fix, but didn’t change the outcome — still zero executions. - Process/Task-level config — compared field by field (TableName, ForEntireTable, Scope, TimeoutSeconds, MaxRetryCount, CreatedBy, Inputs, AlwaysRunAsDeployed, IsEmbedded) across multiple affected Bots. All consistent, no anomalies.
- Our Apps Script backend — confirmed the Web App URL in the Task matches our current active deployment exactly, and its own Executions log shows 0 executions received in the last 7 days, even right after we force-retriggered several Bots today. So AppSheet itself is never sending the HTTP request — this isn’t a receiving-end rejection.
- AppSheet plan/tier — “Analyze app features” under Manage > Author shows our current plan (AppSheet Core) as “ALLOWED” for this feature set, same as Enterprise.
- Google Workspace Admin Console security policies — “Restrict access by external accounts” is unrelated (governs external-account connector access, not outbound webhooks). “Core security” toggle is OFF (requires an AppSheet Enterprise Plus / Workspace Enterprise upgrade we haven’t purchased, so that whole policy suite is inactive on our account).
- Table-level Security Filters — no consistent correlation between having an active filter and whether the Bot works (one filtered table’s Bot works, another filtered table’s Bot doesn’t, and an unfiltered table’s Bot also doesn’t).
- The “AppSheet Core license security settings” governance setting (
APPSHEET_DEFAULT_CORE_GOVERNANCE_SETTING) in the Admin Console — its description explicitly mentions restricting external data connections, which sounded very relevant, but it’s set to OFF, and the Admin Console audit log shows zero changes to it (in fact zero admin events of any kind related to AppSheet) anywhere near 2026-06-11.
Questions for anyone who’s hit this or knows the internals:
- Has anyone else seen webhook-calling Bots silently stop being attempted (not just failing) app-wide, while non-webhook Bots keep running fine?
- Is there any known account-level or App-level restriction, quota, incident, or policy block that could cause this on a Core-plan app?
- Any tips on getting AppSheet’s own backend logs checked for an App ID, since Support access is otherwise routed through our Workspace reseller and hasn’t been able to look into this directly yet?
App info: AppSheet Core plan, App ID (PII removed by staff), deployed (not prototype).
Thanks for reading this far — happy to share screenshots, the reduxStore JSON for the affected Events/Processes/Tasks, or anything else that helps.