Shopify Flow condition metafield blank? Prove the condition path, owner, empty value, and run result.

Use this page when Flow run history shows the workflow entered the condition step and the metafield value used in that condition is empty, null, or whitespace. If the trigger never fires or the metafield is blank on the trigger payload, start with Flow trigger metafield blank. If an action cannot find the key to write, use Flow action metafield missing.

Capture one run ID, workflow name, trigger resource type and ID, condition step name, exact field path, operator, expected value, and whether Admin shows blank, null, empty string, or a value the condition still rejects. Do not overwrite a live metafield before proving the owner the condition reads.

Write down the workflow name, whether it is active, the trigger, and the condition that references the metafield. Confirm the condition path points at the same owner type the trigger provides (order, customer, product, variant, company, and so on). A blank value on a wrong related resource is not a definition bug.

Use one synthetic, reversible test resource. Record its ID, the workflow run ID, the condition expression, and the exact Admin URL for the metafield. Keep customer data, credentials, and private tokens out of screenshots and logs.

Record the definition namespace and key exactly, including case, type, validations, list/reference shape, owner type, and app ownership. Confirm whether Admin shows a saved value, a cleared value, or never-saved. A label that looks right or a value on a different product/order/customer is not proof.

Check whether Flow can read that owner and metafield given app scopes and Admin access. Treat absent key, null, empty string, empty list, and wrong type as separate observations. Do not paste secrets into Flow notes or condition comments.

Open the run details and compare the condition field path with Admin. Verify the condition did not point at a related resource, a misspelled namespace.key, or a type Flow coerces differently (boolean vs string, list vs scalar, money vs number). A stale run, delayed metafield write, or operator that treats empty as false can make a saved value look like a miss.

Separate blank input from operator failure: if Admin shows empty for the field, fix owner, definition, access, or saved value first. If Admin shows a non-empty value but the condition still fails, that is a path, type, or operator issue—not a blank metafield.

Trigger one known-valid resource through the workflow. Record workflow name, run ID, owner ID, namespace.key, type, saved vs blank state, condition path, operator, result, and Admin screenshot. Retry only after the first trace is captured.

Classify the miss as never-reached condition, wrong owner/path, never-saved value, cleared value, access, type parsing, operator mismatch, or timing. Keep it distinct from a blank trigger field and from a missing action write key.

Stay DIY when one workflow, condition path, owner, definition, access, or operator check explains the blank. Keep the proof packet so later Flow edits are reversible.

Pay for the $997 one-time install when several Shopify surfaces, apps, and ops alerts need to be wired and documented on one live store. Nico at Latch AI Ops can trace the agreed Flow condition path in a 72-hour window after collaborator access. No earnings claim, conversion guarantee, or theme rebuild is included; owner passwords are not requested.