Skip to content

Loading Widget is not shown when API Backend Query reruns after Rebuild Current Page #7469

Description

@KLewin1975

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

I have an API Backend Query on a page that depends on a Page State variable.

When I update the Page State using Update Page State → Rebuild Current Page, the API Backend Query correctly runs again with the new parameter.

However, the configured Loading Widget is not displayed while the new API request is running. The old query results remain visible until the new response arrives.

Expected Behavior

When Rebuild Current Page causes a Backend Query to execute again, its configured Loading Widget should be displayed while the query is loading, just as it is during the initial page load.

This is particularly important on slow or unstable connections, because currently there is no indication to the user that new data is being loaded.

Steps to Reproduce

  1. Add an API Backend Query to a page.
  2. Use a Page State variable as one of the API parameters.
  3. Configure a Loading Widget for the Backend Query.
  4. Change the Page State variable using an action with Rebuild Current Page.
  5. The API query runs again correctly.
  6. The Loading Widget is not displayed while the new request is running.

Reproducible from Blank

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

Bug Report Code (Required)

IT4oycmAsIVIvsdA7c/Qae9WiSQXQ3p+a4IrlcpBZywgfZzzBLN/fPfQP1hWTe2idFFqO1qmp14KpqHRiPPDKMFfaCmbGZhGzroIWD3MRlulb4uTF7mKeXwnDcpRIBWl1razvh5NLtFeW00t1FOULujLbBXaJITVIno4Sq/LZO4=

Visual documentation

Attached video shows the API Backend Query being re-triggered after a Page State change. The old data remains visible until the new API response arrives, while the configured Loading Widget is never displayed

FF_bug_report_compressed.mp4

Environment

- FlutterFlow version: Current web version (September 3, 2026)
- Platform: Web
- Browser name and version: Google Chrome 152
- Operating system and version affected: Windows 11

Additional Information

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: needs triageA potential issue that has not been confirmed as a bug.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions