Bug: Parallel Action Flow Confused with Loop — Blocks Renaming and Correct Output

[Kato-Official]

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've encountered an issue when attempting to create a Parallel Action. The system appears to misinterpret the action flow as a loop, which not only disrupts the intended logic but also prevents renaming the action once it's created.

Additionally, when used in typical scenarios—such as fetching documents from Firebase or any database—it fails to retrieve the correct records. It used to work just fine, but now no longer.

Expected Behavior

To create a parallel action to simply fetch two documents.

Steps to Reproduce

1. Create action in the actions flows section and tap parallel action
2. Try edit the name of the action, it will show as Loop 0
3. Try fetching multiple docs from firebase (try with only 2) it will not fetch the right docs.

Reproducible from Blank

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

Bug Report Code (Required)

ITFTjsmAsItNm7RG+KnTKPpvoCEUGUMcWOdEl+tuZwgbIoznBu0XdfekbkluZN+laVNcJE6lo3wGpeiPjYTuG/Y7G0+tGdlm1odTEwvke2inRpSRPIeWQEZBGcFYf3ax0bW7swpROtNidEY+wHGECunJYBbDFOu/Zwh9f6PHaOI=

Visual documentation

This is from FlutterFlow Desktop:

From.FlutterFlow.Desktop.mp4

This is from FlutterFlow Web:

From.FlutterFlow.Web.mp4

Environment

- FlutterFlow version: FlutterFlow v5.4.4 released April 22, 2025 Flutter version is 3.27.3
- Platform: All
- Browser name and version: Chrome
- Operating system and version affected: Mac & web, have not tested on windows, however I suspect the same.

Additional Information

Hi, hope all is well.

I’d appreciate it if you could kindly clarify the expected outcome for this ticket at your earliest convenience. Specifically, could you let me know whether:

• it will be closed as not reproducible,

• considered as functioning as intended,

• marked as not planned for resolution,

• or kept open pending a future update in hopes of a fix,

• transferred to customer support, which will then transfer to bug report,

• or alternatively, left inactive for an extended period before being closed for any reason?

Whilst I'm 100% sure, you are doing your best the human resources available, having this clarity will help me determine whether I should proceed with alternative approaches—such as ditching parallel actions using a simpler synchronous hierarchical structure at performance expense (For your information, the issue does not occur when using a regular (sequential) action flow instead of a Parallel Action. In this case, the actions execute as intended. However, the trade-off is reduced performance, as each step must complete synchronously before the next can proceed)

Thank you in advance for your guidance.
Cheers.

[Kato-Official]

Hi, hope you’re doing well.

I just did a full sweep of our project and found that every single instance of a previously used Parallel Action is now renamed to "Loop Action 0" — even though the original name still shows in the top section UI.

This means:
👉 I now need to manually recheck every action flow where a parallel action was used — to make sure the logic, document calls, variable assignments, and state handling are still functioning as originally intended.

⚠️ This appears to be a regression bug introduced in the latest FlutterFlow updates.

Please double-check your flows if you’re using parallel actions. This one might quietly break things behind the scenes.

Personally, if this were just a naming issue, I wouldn’t be too concerned. But seeing that it’s actually affecting how documents are being fetched, that’s worrying...

FYI I also tested it on a brand new project and having the same issue.

[Alezanello]

Hello!

Thanks so much for flagging this—it's definitely a bug. I’ll go ahead and forward it to the engineering team for review and a potential fix.

Really appreciate you bringing it to our attention!

[Kato-Official]

@Alezanello thanks for the prompt reply. Thanks, appricciated. Cheers

[SailMile]

Had the same issue. Especially when having loops inside the parallel action.

[Kato-Official]

@SailMile I've spoken to support as well and apparently they are currently working on it, I hope with next update will be fixed, in the meantime I went ahead and changed the whole logic of every action back to synchronous and consecutive (Regular vertical action basically), I know... it's extremely time consuming, but better then hoping for the logic to work when in production.