Backend Query action publishes with incorrect filter column — reproducible across multiple publish cycles

[marknaghsh-a11y]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

An On Page Load Backend Query action on a detail page consistently publishes with a different filter column than what is configured in the editor, causing every request to fail with a PostgREST 22P02 invalid input syntax error.

Expected Behavior

Request should be: GET [project-url]/rest/v1/v_journal_entries?select=*&id=eq.{uuid}&limit=1

Steps to Reproduce

Page: Journal Detail page, with a page parameter journalEntryID (String)
On Page Load action: Backend Call → Query Rows → view v_journal_entries → filter id = Page Parameter (journalEntryID) → limit 1 → output variable journalDetail
Editor consistently displays this configuration correctly when reopened
Publish the app
Navigate to this page from a list (Observatory) by tapping an item that passes a valid UUID as journalEntryID
Check Supabase logs for the resulting REST request

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT48jMmA7Y9Om9te1s72KMBKhjwXJl87R+cw0O5DRUw8KOPaPOw+Ps/BM0RDQs/hTFY/e02Jo2oW3MKJi9jIV8YrPS2ZGL05yZduWgGWQlO7VKaOFJWvOXZ6RJpMfUyl0qWNnxElWfNvS0YE2WWmJO6RfAPtQZi0OGw4Dq/LZO4=

Visual documentation

Environment

- FlutterFlow version: N/A — FlutterFlow web app (continuously deployed, no user-facing version number). Project ID: loginegosupreme-7c6j7x. Bug observed June 17, 2026.
- Platform:web
- Browser name and version:chrome latest Safari latest
- Operating system and version affected:

Additional Information

No response

[Juansarmi]

Hi!

Sorry to hear you're experiencing this issue.

To continue the investigation in the most effective way, could you please reproduce the issue in a new blank project and send me the Bug Report Code from that new project?

This will help us isolate the cause and proceed with further troubleshooting.

Kind regards