Wiring-review preflight requires every declared page param to be passed by Navigate, even when not Required

[maxmarion01]

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

Project: Stride (stride-y1psji)

Editing certain pages via the FlutterFlow AI CLI tool (flutterflow ai run) fails preflight with "may be missing param X" for a page's existing Navigate action -- even though X is confirmed NOT marked Required in that target page's own parameter settings, and there is no way, in either the AI tool or FlutterFlow's standard visual editor, to explicitly supply "nothing" for that param.

Affected pages: Dashboard, CasesList, ReferencesList, ModuleListNew, ClinicalToolsList. All have a per-row Navigate action that only passes the one param relevant to that row (e.g. toolRef); the target page also declares journeyRef/unitRef/journeyUnitItemRef/unitOrder, used only when reached from an actual journey context (confirmed correct elsewhere: Units -> ModuleContentOverview passes real values for these same params). This already works fine live; any edit at all to the source page re-triggers a full-page wiring-review that flags it.

Expected Behavior

Preflight should not fail for a Navigate action that omits a target page's non-Required parameter. Either wiring-review should only flag params actually marked Required, or there should be a supported way (in the AI tool and/or the standard editor) to explicitly mark a param as intentionally omitted for a given Navigate action.

Steps to Reproduce

1. Open the ClinicalToolsList page (or Dashboard/CasesList/ReferencesList/ModuleListNew) in the FlutterFlow AI CLI workspace.
2. 2. Note its existing Navigate action to ClinicalToolV2 (or the equivalent target page) passes only one param (e.g. toolRef), while the target page declares 4 more (journeyRef, unitRef, journeyUnitItemRef, unitOrder), none marked Required.
3. 3. Make any edit at all to the source page via flutterflow ai run (even something unrelated to this action) and attempt to push.
4. 4. Preflight fails: "Navigates to ClinicalToolV2 but may be missing param 'journeyUnitItemRef'; ... 'unitRef'; ... 'journeyRef'; ... 'unitOrder'" -- even though the app already works fine live with this exact wiring today.
5. 5. Attempted fix 1: add a default value to those 4 params via app.editPageParams + docRef(...).withDefault(null) -- crashes the compiler with a Stack Overflow (reproducible via flutterflow ai validate).
6. 6. Attempted fix 2: patch only the missing params onto the existing Navigate action via page.mutateNode -- fails a different validator: "Parameter 'journeyRef' passed by Container action to CaseChallenge does not exist", despite journeyRef genuinely existing on the target page with that exact key.
7. 7. Attempted fix 3: replace the whole action via page.ensureActions with all 5 params explicit (real value for toolRef via ItemRef()['reference'], explicit null for the other 4) -- fails with "Item field access 'reference' used outside a ListView builder".
8. 8. Checked FlutterFlow's own visual editor directly: the 4 params are confirmed NOT Required, there is no default-value field for DocumentReference params, and the action's Parameters panel only supports one value per already-referenced param -- no way to add a mapping for an additional, unused param either.

Reproducible from Blank

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

Bug Report Code (Required)

CAES3BRDaEZNYVhOMFZtbGxkMTl5ZW5WaVp6VTVkQkxqRFFvU1EyOXVkR0ZwYm1WeVgzVm9OekI0YW1ObkV2b0lDZ3hTYjNkZlkzRnRaR3g2ZG5vU3JnTUtFa052Ym5SaGFXNWxjbDl3YW04eGVUTm1keExYQVFvUFEyOXNkVzF1WHpSbGJtWjVibmRoRXFNQkNnMUpZMjl1WHpJMmJtMTZNR0ZrR0FnaWlRRTZYeW9KQ1FBQUFBQUFBRHBBTWdRS0FoQUJPa3dLU2dqeDRRTVNFRVp2Ym5SQmQyVnpiMjFsVTI5c2FXUWFGR1p2Ym5SZllYZGxjMjl0WlY5bWJIVjBkR1Z5SUFBcURRb0xjM1JsZEdodmMyTnZjR1V5QzNOMFpYUm9iM05qYjNCbFdnNVNDUWtBQUFBQUFBQVFRSUlCQUhJV0dna0pBQUFBQUFBQUFBQWlDUWtBQUFBQUFBQUFBRG9FYVdOdmJoZ0VJaHdpQWlnQmNoWWFDUWtBQUFBQUFBQUFBQ0lKQ1FBQUFBQUFBQUFBR0FFaXRnRUtnUUVLTEFvVUloSUpBQUFBQUFBQVJrQVpBQUFBQUFBQVJrQVNGQ0lTQ1FBQUFBQUFBRVpBR1FBQUFBQUFBRVpBRWprU0RTZ0NXZ2tKQUFBQUFBQUFKRUJhQUdJQ0VBRnFCQW9DRUFWeUNBb0NFQUVhQWhBQmVoSUpBQUFBQUFBQUFFQVpBQUFBQUFBQUFFQWlBRklBYWhJSkFBQUFBQUFBV1VBWkFBQUFBQUFBV1VCeUZob0pDUUFBQUFBQUFBQUFJZ2tKQUFBQUFBQUFBQUQ2QXdEeUJSUVNFZ2tBQUFBQUFBRHdQeGtBQUFBQUFBRHdQMklBd2dFQUVyMEVDZzlEYjJ4MWJXNWZORzF6Ykc1b04zVVN3UUVLRFZSbGVIUmZiSGxuWkdZMGIzQVlBaUp3RWxSQUVLZ0JBTklCTEFvVVUyaHZkV3hrWlhJZ1NXMXdhVzVuWlcxbGJuUWFGRk5vYjNWc1pHVnlJRWx0Y0dsdVoyVnRaVzUwMmdFSkNRQUFBQUFBQURGQTRnRUVDZ0lRQjRJQ0FnZ0NvZ0lDQ0FiQUFnSDZBd0R5QlJRU0Vna0FBQUFBQUFEd1B4a0FBQUFBQUFEd1AySUF3Z0VBbWdJMkdpMEtDMk5zWVhWa1pTMWpiMlJsRWd0RGJHRjFaR1VnUTI5a1pSb0FJZ2N5TGpFdU1qWXpLZ1l3TGpBdU5EQWd2N1h6eW9jMEV2b0JDZzFVWlhoMFgzcDBZVzluZW5adUdBSWlxQUVTZEVBUHFBRUEwZ0ZZQ2lwQlkzVjBaZUtBazBOb2NtOXVhV01nd3JjZ1RHOTM0b0NUU0dsbmFDQkpjbkpwZEdGaWFXeHBkSGthS2tGamRYUmw0b0NUUTJoeWIyNXBZeURDdHlCTWIzZmlnSk5JYVdkb0lFbHljbWwwWVdKcGJHbDBlZUlCQkFvQ0VBR0NBZ0lJQXFJQ0FnZ0d3QUlCV2haQUFWb1NDUUFBQUFBQUFDaEFHUUFBQUFBQUFDaEErZ01BOGdVVUVoSUpBQUFBQUFBQThEOFpBQUFBQUFBQThEOWlBTUlCQUpvQ05ob3RDZ3RqYkdGMVpHVXRZMjlrWlJJTFEyeGhkV1JsSUVOdlpHVWFBQ0lITWk0eExqSTJNeW9HTUM0d0xqUXdJTzd1ODhxSE5CZ0VJbUlpSEJBQkdBUW9BVElVS2hJSkFBQUFBQUFBRUVBWkFBQUFBQUFBRUVCYUdVQUJTaElKQUFBQUFBQUFLRUFaQUFBQUFBQUFLRUNDQVFCNkNCZ0JJZ1FJQkJnRStnTUE4Z1VXRWhJSkFBQUFBQUFBOEQ4WkFBQUFBQUFBOEQ4YUFPSUdBR0lBd2dFQUdBTWljaG9DS2dCYVVrQUJTaElKQUFBQUFBQUFNRUFaQUFBQUFBQUFNRUJTRWdrQUFBQUFBQUFvUUJrQUFBQUFBQUFvUUZvU0NRQUFBQUFBQURCQUdRQUFBQUFBQURCQVloSUpBQUFBQUFBQUtFQVpBQUFBQUFBQUtFRDZBd0R5QlJRU0Vna0FBQUFBQUFEd1B4a0FBQUFBQUFEd1AySUF3Z0VBR0FFaXJ3TUtuUUVLRmdvVUloSUpBQUFBQUFBQThIOFpBQUFBQUFBQThIOFNVUklOS0FKYUNRa0FBQUFBQUFBb1FGb3dNZ2tKQUFBQUFBQUE4RDg2QkFvQ0VBcENFZ2tBQUFBQUFBQUFBQmtBQUFBQUFBQUFBRW9KQ1FBQUFBQUFBUEEvWWdJUUFXb0VDZ0lRQlhJRUNnSVFCU0lORWdzaUNRa0FBQUFBQUlCYlFGSU5FZ3NpQ1FrQUFBQUFBSUJWUUdvU0NRQUFBQUFBQUZsQUdRQUFBQUFBQUZsQVdpOUtDUWtBQUFBQUFBQW9RRklKQ1FBQUFBQUFBQ2hBV2drSkFBQUFBQUFBS0VCaUNRa0FBQUFBQUFBb1FJSUJBSklEdXdFYXVBRVNzd0VJQ2xLdUFSSStFandJQ2xJNEVpa1NKd2dIUWdwQ0NBb0djZ1FJQXlBQWdnRVdDaFJEYUc5cFkyVkRhR2x3YzE5dU0zSnlkRFpqWmhJSENnVVNBMEZzYkNJQ0NBRVNhQkptQ0FwU1loSXBFaWNJQjBJS1FnZ0tCbklFQ0FNZ0FJSUJGZ29VUTJodmFXTmxRMmhwY0hOZmJqTnljblEyWTJZU01SSXZDQVJDQWhJQVNoR0NBUTRLREFvS1ltOWtlVkpsWjJsdmJvSUJFd29SVEdsemRGWnBaWGRmY25wMVltYzFPWFFpQWdnQk1nSUlBaGdCK2dNQThnVVdFaElKQUFBQUFBQUE4RDhaQUFBQUFBQUE4RDhhQU9JR0FHSUFpZ0dWQVJLT0FRb0ljM1V5ZUhadmRXY1NnUUVTZEJBQkdsa1NRZ29HYVhWb1ozUXdFamdLRVFvSGRHOXZiRkpsWmhJR2FYVm9aM1F3SWlNSUJFSUNFZ0JLQllJQkFoQUJnZ0VUQ2hGTWFYTjBWbWxsZDE5eWVuVmlaelU1ZERJVENoRlRZMkZtWm05c1pGOTFOMlp5YlhWbmFpQUFXaE1LRVZOallXWm1iMnhrWDNVM1puSnRkV2RxcWdJSWQzTjBNSGR6Y25VYUFnZ0J3Z0VBR0FZaVVVSXJFQUlZQUNvZktoSUpBQUFBQUFBQThEOFpBQUFBQUFBQThEODZDUWtBQUFBQUFBQkdRRG9FQ0FFWUFWb0RnZ0VBK2dNQThnVVdFaElKQUFBQUFBQUE4RDhaQUFBQUFBQUE4RDhhQU9JR0FGSndDaU55SVJJQ0NBY3FHd29aQ2cxamJHbHVhV05oYkZSdmIyeHpFZ2cyTlRZd2MzRndjaEpKQ2hrS0RXTnNhVzVwWTJGc1ZHOXZiSE1TQ0RZMU5qQnpjWEJ5R2drS0J3b0ZiM0prWlhJb0FISWZDaHNLR1FvTkNndHBjMUIxWW14cGMyaGxaQkFCT2dZU0JIUnlkV1VRQVdJQXdnRUE=

Visual documentation

No screenshots/video captured (this was reproduced entirely via the FlutterFlow AI CLI tool + a scripted check of the visual editor's Action/Parameter panels, not a click-through repro). Full terminal output + editor findings below:

Stride project (stride-y1psji) -- terminal output from the three failed fix attempts.

=== Attempt 1: default value on target page params ===
Approach: app.editPageParams + docRef(...).withDefault(null) on the 4 unused
DocumentReference params (journeyRef/unitRef/journeyUnitItemRef/unitOrder) on
the target page (e.g. ClinicalToolV2).
Result: `flutterflow ai validate` crashes the compiler with a Stack Overflow.
Isolated to that exact call -- removing it makes everything else compile fine.

=== Attempt 2: patch only the missing params onto the existing Navigate action ===
Approach: page.mutateNode, adding only the 4 missing param keys directly onto
the existing Navigate action, leaving the working param (e.g. toolRef)
untouched.
Result:
  Error: Parameter 'journeyRef' passed by Container action to CaseChallenge does not exist.
This is incorrect -- journeyRef genuinely exists on CaseChallenge (and on
ClinicalToolV2) with the exact key already used successfully for other
params on the same action (confirmed via `flutterflow ai inspect` and via
FlutterFlow's own web editor Page Parameters panel).

=== Attempt 3: replace the entire Navigate action ===
Approach: page.ensureActions replacing the whole action on the per-row
Container's ON_TAP trigger with a complete Navigate call listing all 5 of
the target page's params -- toolRef via ItemRef()['reference'] (the tapped
row's own document reference, matching the existing generated Dart:
`listViewClinicalToolsRecord.reference`), explicit null for the other 4.

$ flutterflow ai test
00:00 +0: loading test/app_test.dart
00:00 +0: test/app_test.dart: starter DSL app compiles
00:00 +1: All tests passed!

$ flutterflow ai run dsl/edit.dart --project-id stride-y1psji --commit-message "..."
Workspace binding: stride-y1psji.
Resolved target mode: existing (existing project stride-y1psji).
[FAIL] compileDslApp (951ms)
    Error: Bad state: Item field access "reference" used outside a ListView builder.
Error: Bad state: Item field access "reference" used outside a ListView builder.

No push occurred in any of the three attempts (all failed before the push
step, so the live project was never mutated by any of these attempts).

=== Confirmed directly in FlutterFlow's own web editor (not just the AI tool) ===
- Selected the ClinicalToolsList row's Container -> Actions tab -> "Navigate
  To ClinicalToolV2" -> Parameters section shows only `toolRef *`.
- The dropdown next to that one Parameters row lets you re-point it to a
  DIFFERENT single target param (toolRef / journeyUnitItemRef / unitRef /
  journeyRef / unitOrder) but there is no way to add a second, third, fourth
  mapping alongside it.
- The "+ Define" button next to Parameters does not add a value mapping for
  an already-declared-but-unused param -- it jumps to the destination page's
  own "Define Parameters" screen (for declaring brand-new page params, which
  is not what's needed here, since all 5 already exist).
- On that destination page's own Define Parameters screen: selecting
  journeyRef (or unitRef / journeyUnitItemRef / unitOrder) shows "Required"
  UNCHECKED, and there is no default-value field at all for a
  DocumentReference-typed parameter.

So there is no configuration available, in either the AI tool or the
standard visual editor, that satisfies what the AI tool's wiring-review
preflight is demanding.

Environment

- FlutterFlow version:  v7.0.79 (released Sep 11, 2026); AI CLI SDK build c40fa0b8 / 0.0.40+2, confirmed latest via flutterflow ai upgrade --check
- Platform: Web (FlutterFlow project editor + the FlutterFlow AI CLI tool, package flutterflow_ai)
- Browser name and version: Chrome (latest)
- Operating system and version affected:  macOS

Additional Information

No response

[Alezanello]

Hi! 👋

Thanks for one of the most thorough investigations we've seen on this tracker — the three distinct fix attempts with full terminal output made this straightforward to verify.

What we confirmed: you're right on every count. ClinicalToolV2Widget's constructor genuinely has toolRef as required and the other four (journeyUnitItemRef, unitRef, journeyRef, unitOrder) as plain optional nullable parameters — exactly matching "not marked Required."

Going to send to the engineer team for a fix
Thanks a lot