Resume or close one launch attempt safely

Before you start

• The owning account and saved attempt reference.
• Fresh server status and current authority for any recovery action.

Keep the same attempt

Open the attempt from My launches or its saved link. Read the error before using any action. Resume preparation, when offered, keeps the saved mint, publication records and original consent ceiling; it does not create a token or increase authorized spend.

Resume requires a fresh authorized state and connected status stream. If unavailable, retry the status read and preserve the attempt. Start a new launch or clearing a draft does not safely release the original reservation.

1. Find the original attempt, not a new wizard draft.
2. Refresh its status and check the stream is connected rather than stale or resyncing.
3. If Resume preparation is offered and its existing ceiling is understood, use it once. Otherwise keep the record and review the blocker.

Check publication without authorizing another payment

Preparation must publish and verify the exact public image and metadata JSON before signing. Local image selection, a saved upload or an upload receipt is not public verification. Use Check publication status again on that same attempt.

Checking status does not authorize an upload or payment. Closing the page does not cancel preparation. If a mint is already confirmed, keep it while platform finalization continues; missing external artwork is a different issue.

Stale status is not lost ownership

A transient status read or stream failure can retain labeled stale information while reconnecting. Do not restart the launch based on that stale record. Retry the read and wait for authoritative resync before mutation.

An authentication or access-denied response is different: private cached content is hidden rather than treated as authorized. Check that you are signed into the original owning account. A missing/denied record does not prove cancellation, release or refund.

1. Read the stream and error labels, not only the last visible status.
2. For a temporary read failure, retry or allow reconnection without another submission.
3. For an access error, check the account identity and reopen the saved link. Never share account credentials or private signing material to restore access.

Request cancellation; verify the outcome

Request / recheck cancellation is a guarded action for an exact attempt. The server checks signatures, submitted payments, mint evidence and remaining claims before safe release. Uncertain outcomes remain held; a request acknowledgment is not release.

Read remaining reserved amounts, name reservation, authority claims, nonrefundable spend and refund rows separately. A reservation release is not a refund transaction. Refunds can remain pending and already-paid network fees cannot be reversed.

1. Use the original attempt’s cancellation control only when offered.
2. Read and acknowledge the exact-attempt warning, then request or recheck cancellation.
3. Refresh and inspect the returned cancellation state and reason. Verify any actual refund signature and original-payer destination independently.
4. If status is uncertain or a safety check fails, preserve the hold and recheck; do not assume a new launch is safe.

Review a recovery plan before execution

Recover stuck launches previews candidates and the proposed per-attempt actions. Previewing is not execution. Check each selected attempt, the acknowledgment and the plan’s expiry before using the offered recovery action.

An expired plan must be refreshed and reviewed again. Read individual outcomes and refresh balances afterward; partial success or a mutation/read error does not mean every attempt was refunded. Do not repeat execution just to correct a stale balance display.

1. Open the recovery panel in your launch account view and preview a plan.
2. Inspect candidates and select only the intended attempts. Read the plan warning and expiry.
3. Execute only a valid reviewed plan, then inspect each outcome. Use status reads for unresolved attempts.

Historical reserve obligations remain separate

Old standard or reserve-funded attempts can show held supply/share, acquisition budgets, settlement costs and original-payer refunds. These are existing obligations, not instructions to open a new standard launch or buy a reserve for new reward issuance.

An obligation row without a payment signature is not proof of payment. Reserve-short or failed settlement can keep a desk disabled. Follow only the authorized existing-attempt recovery controls; operator repair tools are not a public launch workaround.

Related guides