Skip to content

Refresh Database Request action does not respect Wait For Result = true #5820

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2 tasks done
timdcochran opened this issue May 14, 2025 · 1 comment
Open
2 tasks done
Labels
Bug status: confirmed Issue has been reproduced and confirmed as a bug.

Comments

@timdcochran
Copy link

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

The Refresh Database Request action does not wait for the call to refresh when Wait For Result is enabled.

Expected Behavior

The action blocks the action chain until the database request is refreshed.

Steps to Reproduce

See project ID await-query-refresh-1n4reh

  1. Configure a backend query on a widget.
  2. Create a button with an action change that writes a timestamp to the console, refreshes the backend query with wait for result enabled, then writes another timestamp to the console.
  3. The console timestamps will be immediate even when the database request is not:
    console:
    flutter: start 2025-05-14 18:08:36.759000
    flutter: end 2025-05-14 18:08:36.813000

dev_tools network:
Start time: 18:08:36.798
End time: 18:08:39.266

Reproducible from Blank

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

Bug Report Code (Required)

IT4Wl8+Az49ItbxI0KruYMZR/SkvJlA2U40zjcN9Zw03B5DyP5wPX/z4UBJoTbyndkFMM2KJuGYdp87Lm9z1DcEFC0yubrk+zKVuQzvMbGqQMJObCrmWYUF+GshNClSl58Gn2QlvBNBic3gS2jimNuuWSivtJO/1O1YvOOWJJoPXrgfuQ0SLb3kNh1JWeC/v

Visual documentation

None needed

Environment

- FlutterFlow version: v5.5.1
- Platform: iOS app
- Browser name and version: n/a
- Operating system and version affected: macOS

Additional Information

No response

@timdcochran timdcochran added the status: needs triage A potential issue that has not been confirmed as a bug. label May 14, 2025
@Alezanello Alezanello self-assigned this May 14, 2025
@Alezanello Alezanello removed the status: needs triage A potential issue that has not been confirmed as a bug. label May 14, 2025
@Alezanello Alezanello added status: confirmed Issue has been reproduced and confirmed as a bug. Bug labels May 14, 2025 — with Linear
Copy link
Collaborator

Thank you very much for providing the test project. I can confirm that this is a bug, and I will forward it to the engineering team for further investigation. Thanks again for your help!

@Alezanello Alezanello removed their assignment May 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug status: confirmed Issue has been reproduced and confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

2 participants