New App Builder published backend appears to reuse stale prepared statement

💬 App Building
,
2

Summary

In Retool's new App Builder (Cloud), a published Restaurant Staff Management app returns a stale error on CLOCK IN — "bind message supplies 5 parameters, but prepared statement requires 12" — even though the current backend function uses exactly 5 placeholders/parameters, a corrected new function (attendanceV2) was created, the frontend was repointed to it, and the app was republished multiple times. The deployed runtime appears to be executing an older version of the backend code.

AI Response

This matches a known synchronization behavior in the new App Builder where manual edits to backend function (.ts) files don't reliably persist and the runtime keeps executing an older committed version, even after repointing the frontend to a new function. Manual Code tab edits are tracked in Change History alongside agent edits, and there can be a delay before an edit is actually persisted via a commit — until it commits, the previous version continues to run. Before republishing, open the Change History drawer and confirm the corrected attendance/attendanceV2 code is actually recorded as a committed change under your name (not still pending, blank, or overwritten by an agent edit); make edits only when no agent operation is running, and avoid editing view-only files. Once the corrected version is confirmed committed in Change History, republish so the deployed runtime picks up the current source rather than the stale prepared statement.

Sources

:bookmark: Subject: App Builder backend function edits are reverting / not persisting
A new App Builder (Cloud) report of the same behavior — backend .ts edits reverting/reopening blank and the Timeline/Preview executing an older synchronized version even after the frontend was repointed to a new function — with staff confirming edits can lag until committed, visible in the Change History drawer.
:bookmark: Manually edit app code | Retool Docs
Documents manually editing app code in the new App Builder's Code tab, including how Change History distinguishes user vs. agent edits and how agent regeneration or view-only files can cause manual backend edits to appear not to save.

The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a :heart:, :+1:, or :-1:. Or by marking this post as the "Solution"! Let us know if you have any feedback here. :rocket: