Live P1

Read Live Log and recover failed work

Separate normal progress, a safe retry, a queued dismissal, and an unknown external outcome.

Availability
Live
Last verified
Runtime anchor
ab084f79c5ed3fc6a28f07c64b29920944a0e5db
Certification anchor
db23559179dc3c67be8a1ab16a0f07323b9820f7
Evidence note
Production logs and a normal successful drop were browser/real-write verified; final certification did not force every provider recovery branch.

What this does

Separate normal progress, a safe retry, a queued dismissal, and an unknown external outcome.

Before you begin

  • Keep the active store and artwork filename available when investigating a failure.
  • Open provider/store accounts in read-only mode before retrying a create failure.

What changes outside ArtDrop

Reading logs is local. Retry can continue a proven-safe stage and may write externally. Dismissal hides/removes an ArtDrop attention item when its queued command is accepted; it does not undo external objects.

ArtDrop Activity page showing worker status, queue depth, processed artwork, and error count
Processing activity. Activity summarizes processing health and queue counts; opening it is read-only and the technical log stays available for diagnosis.

Steps

  1. Read the current state

    Use Live Log for processing stages, Copy Log for copy events, and Needs Attention for actionable failures. Use Full Log for longer history.

  2. Confirm external reality

    For provider or Shopify create/update failures, check whether the object already exists before clicking Retry.

  3. Retry only a known-safe item

    Choose Retry when ArtDrop identifies a retryable known stage. Treat Retry queued as acceptance of a command, not proof of completion.

  4. Dismiss only after disposition

    Choose Dismiss after the issue is understood or intentionally abandoned. Dismissal queued is not an external cleanup receipt.

Expected result

The item either advances to a recorded result, remains in Needs Attention with a stable reason, or is dismissed after an explicit decision.

Limits and non-goals

  • An HTTP timeout after create can be an ambiguous outcome; absence of an ArtDrop success response does not prove nothing was created.
  • Logs can contain operational identifiers; redact them before sharing screenshots.

Troubleshooting

  • For an unknown create outcome, stop automatic retries, capture time/store/file/error, inspect the provider, and contact support.
  • For repeated credential errors, test the connection and revoke/replace the credential outside ArtDrop.
ArtDrop Activity page showing a clear temporary-unavailable status and Refresh recovery control
Activity recovery state. A temporary health-read failure is shown explicitly with Refresh; it does not claim queued work was deleted or safely replayed.

How to undo or clean up

Dismiss changes ArtDrop’s attention list only. Delete or correct external objects in their owning service.