campaign operations

Understand failed jobs and retries

Learn how to understand failed jobs and retries with a safe Juniper & Trail example, shopper impact, options, and recovery checks. A failed background phase records a classified failure. Retry recoverable Shopify or network failures; reconnect authorization instead of repeatedly retrying an AUTH_REVOKED failure.

Before you begin

• Review campaign completeness and product preview
• Confirm authorization and theme status
• Know the restore consequences of the chosen discount route

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

   Use the summary cards to check live, scheduled, and sale-product totals.

2. 2

   Inspect the active campaign and use its view, edit, revert, or end actions.

3. 3

   Check theme embed, badge, banner, background-job, and countdown health.

4. 4

   Search and filter past campaigns before opening their records.

1. Open the failed campaign job for the intended shop and confirm the current record and status.
2. Read the failure code and retry only the offered recoverable phase; reconnect Shopify first for AUTH_REVOKED.
3. Read the inline summary, warning, or preflight before submitting; do not repeat a command while background work is running.
4. Confirm the retry resumes from checkpoints without duplicating already-complete writes.
5. Confirm the resulting status and History/audit evidence, then spot-check Shopify or the storefront when the action has external effects.

A failed background phase records a classified failure. Retry recoverable Shopify or network failures; reconnect authorization instead of repeatedly retrying an AUTH_REVOKED failure.

Juniper & Trail example

Juniper & Trail uses understand failed jobs and retries on its controlled Weekend Trail Kit campaign, then checks phase status, History, and two representative storefront products. 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

During activation or revert, storefront components can settle at different moments; use status rather than repeated clicks to determine completion. 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 Understand failed jobs and retries.
• 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

• Resolve overlapping campaign conflicts

Options reference

| Option | Use it when | Consequence | | --- | --- | --- | | Retry | Transient Shopify/network failure | Resumes idempotent work | | Reconnect | AUTH_REVOKED | Required before retry | | Do not repeat | Job is Pending/Running | Avoid duplicate commands |

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.