Shopify Flow trigger metafield blank? Prove the event, owner, value, and payload.

Use this page when Flow run history shows a workflow run or a trigger event, but the expected field is empty, omitted, or unavailable to the next action. If run history is empty because no event matched, use the trigger-not-firing playbook. If the workflow is inactive or broadly broken, use Flow not running.

Capture one run ID, the trigger name, the action that receives the field, the exact field path, and whether the UI shows blank, null, empty string, or an unavailable field. Do not add a duplicate metafield before proving the owner.

Write down the trigger event and resource it actually emits: Order created is not Order paid, Customer tagged is not Order tagged, and inventory events can expose inventory item, variant, or location data. A product metafield will not appear because the workflow reads an order or inventory owner.

Use one synthetic, reversible test resource. Record its ID, the event timestamp, the shop, and the exact run history entry. 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 a saved test value on that same resource persists in Admin or the owning app. A label that looks right, a draft value, or a different resource is not proof.

Check the app and Flow connector scopes required to read the owner. Treat absent, null, empty string, and empty list as separate observations. Do not paste secrets into run notes.

Open the run details and compare the trigger payload field path with the active workflow's selected value. Verify the workflow version is the one running, the app connector is connected, and the trigger exposes that owner on this event. A stale draft, wrong owner, wrong field path, or unsupported type can make a saved value look blank.

Separate input absence from action failure: if the trigger payload is blank, fix owner, definition, access, or event shape first. If the payload contains the value but the next action drops it, that is a mapping or connector issue—not a missing metafield.

Run one controlled event on one known-valid resource. Record the trigger, run ID, owner ID, namespace.key, type, saved test value, payload state, workflow version, connector state, and action input. Refresh or rerun only after the first trace is captured.

Classify the miss as event/owner, definition/value, access, field path, type parsing, stale workflow version, or action mapping. Keep it distinct from a trigger that never creates a run.

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