Runner AI
DocumentationStorefront and publishing

Troubleshoot preview and publishing

Match storefront, build, publication, checkout, and domain states to the safest next action.

Entry path: Workspace → select a store → Storefront → reproduce the preview or publication state shown on screen

What this covers

Identify which layer is failing—project version, preview, build check, publication, public catalog, checkout, or domain—and take the smallest safe recovery action.

Why this distinction matters

The storefront journey has several independent layers. Repeating Publish cannot fix missing product data, and refreshing Preview cannot repair a payment connection. Start with the exact message and surface that failed.

Availability and prerequisites

  • Keep the project open and note the current version label.
  • Record the exact message, page path, and whether it appeared in Preview or on the public URL.
  • Wait for active Runner work to reach Completed, Failed, or Stopped before starting a conflicting recovery action.
  • Do not remove domains, restore versions, or repeat paid actions just to test a theory.

Find the failing layer

  1. In Storefront, check whether a current version exists.
  2. Confirm whether normal Preview opens.
  3. If you are publishing, read the result of the build check before selecting another action.
  4. If publication succeeds, open the public URL rather than the preview URL.
  5. On the public store, test the catalog and cart.
  6. Check Runner's checkout status and the actual checkout path.
  7. If only the custom address fails, check Domain Settings last.

Important recovery controls

ControlWhat happens when selected
Refresh in PreviewReloads the current preview and clears the active Design Mode selection and undo/redo session. Save pending direct edits first.
Fix / Fix errorSends the displayed preview diagnostic to Runner as a repair request. Dismiss only hides the message.
Fix with AICloses the publication confirmation and sends its build failure to Runner for repair; publication does not start.
Retry checkRuns the storefront build check again after Runner could not reach the workspace.
Open Store OperationsCloses the publication confirmation and opens Store Operations so you can complete the named setup.
Retry setup statusChecks Store Operations readiness again after its status was unavailable.
RepublishStarts a fresh checked publication attempt after a failed or linkless result. Fix the named cause first.
Retry checkout statusChecks again for an enabled payment connection; it does not test a product, shipping, or the checkout form.

State-to-action reference

Message or symptomLayerWhat it meansSafest next action
No storefront yetProject versionNo previewable version exists.Ask Runner to build the first storefront.
Building the first version…Project versionRunner is still creating it.Follow task progress; do not publish yet.
Build failed on a versionProject versionThat version is not ready.Open the task details and ask Runner to repair the failure.
Preparing preview…PreviewRunner is starting the selected preview.Keep the latest version selected; refresh only if progress stops.
Failed to load the preview for this versionPreviewThe selected version could not be displayed.Return to current, refresh, or try another ready version.
Reconnecting previewPreviewRunner lost the preview connection and is retrying.Follow the retry count; reconnect the workspace if recovery fails.
Preview error bar with FixPreviewThe running page reported a diagnostic Runner can use.Select Show more to inspect it, Fix or Fix error to send it to Runner, or Dismiss only to hide the bar.
Page not foundPreview or public routeThe path does not exist in that version.Return to /, use visible navigation, and ask Runner to create or repair the route.
Design mode didn't startDesign ModeThe editable preview did not become ready.Select Try Again, or return to current Preview and refresh.
Visual editor disabled while AI is processingDesign ModeRunner is handling another request.Wait for Runner to finish.
Failed to load version historyVersion historyThe version list request failed.Select Try Again.
Restore is blockedVersion historyRunner is active or the version is not ready.Wait for Runner, then choose a ready version.
We couldn't reach your workspacePublication checkRunner could not run the build check.Select Retry check; reconnect the workspace if it repeats.
Something went wrong while building your storePublication checkCurrent storefront cannot pass the build.Select Fix with AI, review the repair, then rerun the checks.
Store setup is incompletePublication setupImportant store operations remain unfinished.Select Open Store Operations. Acknowledge only if the limitation is intentional.
We couldn't verify Store OperationsPublication setupSetup status is unknown.Select Retry setup status before considering an acknowledgment.
No code changes detectedPublication changesRunner found nothing new since the last publication.Cancel, or acknowledge a same-state redeploy only when intentional.
Payment integration is not configuredCheckout setupSome publication flows show this before launch when no enabled payment connection is found.Connect Stripe; use the acknowledgment only for an intentional browse-only launch. Other flows report checkout status after publication.
Store publish failedPublicationThe attempt did not complete.Repair the named issue, then select Republish.
Store link unavailablePublication handoffThe attempt finished without a usable public URL in Runner.Close the dialog, confirm the workspace is ready, then select Republish.
Public store shows old contentPublication or versionThe current project changes are not live.Confirm the latest current version, select Publish Changes, and reopen the public URL.
Product missing on public storeCatalogPublication succeeded, but the intended product is not visible.Check product status, market, price, and inventory; publish changes if required.
Cart action missing or disabledCatalog or availabilityThe selected item cannot currently be added.Check required options, availability, stock, price, and region.
Checkout pausedPaymentThe post-publish flow did not find an enabled Stripe connection.Select Connect Stripe, then retest the actual checkout path.
Checkout status unavailablePayment statusRunner cannot confirm payment readiness.Select Retry checkout status and test the public checkout independently.
Custom domain says MisconfiguredDomainExpected DNS records are not verified.Copy the displayed DNS values exactly to your provider, then recheck.
Transfer in progressDomainA domain is moving between stores.Do not start another transfer; follow the shown status.

Report a problem to Runner

Include these details in one message:

  1. the exact page path or public URL;
  2. whether it failed in Preview or on the live store;
  3. the current version label;
  4. the exact error or state text;
  5. the last button you selected;
  6. the expected result; and
  7. whether the issue reproduces after the documented retry action.

For a visual problem, include the device layout and a screenshot. For checkout, stop before a real charge and report the last successful step.

Recovery boundaries

  • Do not repeatedly resume or republish an unchanged failed state. Fix the named cause first.
  • Do not restore an older version while Runner is working.
  • Do not remove a domain to fix a storefront or checkout issue.
  • Do not claim launch success until the public URL, intended catalog, cart, and required checkout step have each been checked.