Dry runs

A dry run does the work but doesn’t write the result anywhere. Toggle Dry run in the Start run modal.

Dry-run only applies to phases that produce a side effect — transform and load. Extract has nothing to dry-run, so the toggle is ignored when extract is the only phase selected.

Dry-run transform

• The mapping runs against the latest extracted data.
• The output is computed and shown on the run item, but not staged for load.
• Nothing changes in your queue of records waiting to push.

Useful for: previewing mapping changes against the whole catalog without affecting subsequent loads.

Dry-run load

• Each pending record is checked: would it create or update? With what payload? With what conflict resolution?
• Nothing is sent to Shopify.
• The run item logs every intended call so you can audit the destination’s diff before pulling the trigger.

Useful for: cut-over rehearsals. Run a dry load the day before, review counts, then run the real load.

What dry runs cost

Dry runs still hit the source (if extract is included) and still spend time computing transforms. Cost-wise they’re identical to real runs minus the destination side. Use them freely during configuration; reach for transform-only without dry-run for the actual mapping iteration loop.