shopify flow

Trigger Early revert from Shopify Flow

Learn how to trigger Early revert from Shopify Flow with a safe Juniper & Trail example, shopper impact, options, and recovery checks. The Shopify Flow action keeps its historical panic-revert handle for compatibility, but the merchant-facing operation is Early revert and follows the same restore consequences.

Before you begin

• A compatible Badgy plan entitlement
• Shopify Flow installed and permission to edit workflows
• A stable campaign identifier and safe test campaign

Confirm the shop, current status, and intended consequence before changing anything. Use read-only status, preview, or history evidence first.

Step-by-step setup

Open full size ↗

1. 1

   Search campaign sessions and filter their lifecycle or attention status.

2. 2

   Select the campaign session created or changed by the automation.

3. 3

   Verify the selected session state and recorded campaign action.

4. 4

   Inspect product change records when confirming completion or early revert.

1. Open Shopify Flow → Badgy Early revert action for the intended shop and confirm the current record and status.
2. Set Campaign ID for an ACTIVE campaign; the extension handle may retain historical panic-revert naming, while completed/reverted is 200 no-op and invalid state is 4xx.
3. Read the inline summary, warning, or preflight before submitting; do not repeat a command while background work is running.
4. Monitor the priority job, confirm presentation/discount removal and series termination, then restore direct prices separately if needed.
5. Confirm the resulting status and History/audit evidence, then spot-check Shopify or the storefront when the action has external effects.

The Shopify Flow action keeps its historical panic-revert handle for compatibility, but the merchant-facing operation is Early revert and follows the same restore consequences.

Juniper & Trail example

Juniper & Trail tests trigger early revert from shopify flow against a controlled campaign, then confirms both the Flow run and Badgy audit trail before enabling the workflow. The documentation fixture uses realistic products, inventory states, variants, collections, and protected exclusions so the preview exercises the same decisions as a merchant catalog.

What shoppers will see

Flow changes when Badgy receives a command, but the same background activation and revert phases still determine storefront timing. Check the relevant result from product through cart where applicable. For shopper-facing work, compare desktop and mobile and verify both an eligible and an ineligible item.

Common mistakes and troubleshooting

• Acting on the wrong shop. Confirm the Shopify store and campaign before following Trigger Early revert from Shopify Flow.
• Trusting a stale preview. Refresh after catalog, schedule, discount, theme, locale, or market changes.
• Repeating a background command. Read status and History first; retry only when Badgy presents a recoverable failure.
• Skipping the consequence check. Confirm what changes for shoppers and what the end or restore path will do.

If the status reports revoked authorization, reconnect Shopify before retrying. If the result still differs from the preview, preserve the campaign ID and approximate time, then open support from this identified shop. Never send customer data, access tokens, or full catalog exports in feedback.

Related guides

• End a campaign from Shopify Flow

Options reference

| Option | Use it when | Consequence | | --- | --- | --- | | ACTIVE | Valid urgent stop | Priority Early revert job | | Ended/Reverted | Duplicate delivery | 200 no-op | | Non-active | Cannot Early revert | 4xx permanent | | Direct prices | Price mutation campaign | Remain until History restore |

Badgy behavior in this guide is reviewed against the repository's shipped UI, service rules, and feature design documents. Shopify-owned theme, Markets, Flow, billing, and discount behavior can also depend on the store's Shopify configuration; consult the Shopify Help Center for that platform configuration.