Shopify Flow action metafield missing? Prove the action, owner, mapping, and write path.

Use this page when Flow run history shows a workflow run and an action step, but the metafield is absent from the action input, the write fails, or the target resource never receives the value. If the trigger payload itself is blank or the field never arrives from the event, use the trigger metafield blank playbook first. If the workflow is inactive or broadly broken, use Flow not running.

Capture one run ID, the action name, whether the action is a read or a write, the exact field path, the target resource ID, and the error or empty state shown in run history. Do not create a duplicate metafield definition before proving the owner and mapping.

Write down the action and the resource it mutates or reads: Update order metafield is not Update product metafield, Add customer tag is not a metafield write, and Send Admin API request can target a different owner than the trigger. A product metafield will not appear because the action writes an order or customer owner.

Use one synthetic, reversible test resource. Record its ID, the action timestamp, the shop, and the exact run history entry for that action. 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, and app ownership. Confirm the action is allowed to read or write that definition: merchant-owned vs app-owned, access storefront/Admin/API, and whether Flow's connector has the required scopes.

Treat missing definition, wrong owner, type mismatch, validation failure, and insufficient write access as separate observations. A label that looks right or a draft definition is not proof. Do not paste secrets into run notes.

Open the run details and compare the action's selected input paths with the live payload and the active workflow version. Verify the workflow version is the one running, the app connector is connected, and the action supports that owner and type. A stale draft, wrong owner ID, wrong field path, or unsupported type can make a mapped value look missing downstream.

Separate missing input from failed write: if the action never receives the value, fix trigger mapping or field path first. If the action receives the value but the resource still lacks it, that is a write permission, type validation, or wrong-owner issue—not a blank trigger metafield.

Run one controlled event that reaches the action on one known-valid resource. Record the action name, run ID, owner ID, namespace.key, type, intended read/write, input mapping, payload state, workflow version, connector state, and action result or error. Refresh or rerun only after the first trace is captured.

Classify the miss as wrong action/owner, definition/access, input mapping, type validation, stale workflow version, or write failure. Keep it distinct from a trigger that never supplies the field and from a trigger that never fires.

Stay DIY when one action, owner, definition, access, mapping, or write check explains the missing metafield. 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 workflow in a 72-hour window after collaborator access. No earnings claim, conversion guarantee, or theme rebuild is included; owner passwords are not requested.