Status dictionary

Status Meaning What to do
Draft Task is incomplete or not checked Finish configuration
Resolving MintDash is retrieving stage/calldata data Wait; inspect source if it fails
Ready Preflight passed Review spend and timing
Armed Waiting for manual/scheduled fire Avoid unnecessary edits
Running Workers are executing the task Watch per-wallet rows
Submitted RPC accepted a raw transaction Track tx hash; not yet guaranteed
Included Transaction confirmed on-chain Review receipt and PnL
Failed Execution stopped before a successful inclusion Use the exact error class
Dropped/Replaced Transaction was not included or nonce was superseded Inspect nonce and replacement
Settled Post-mint accounting is recorded Review history and portfolio

Diagnose by layer

flowchart TD
	A["Task failed"] --> B{"Was a tx hash produced?"}
	B -- "No" --> C["Resolve, auth, vault, nonce, or simulation"]
	B -- "Yes" --> D{"Was it included?"}
	D -- "No" --> E["Fees, route, propagation, replacement, or sellout"]
	D -- "Yes, reverted" --> F["Contract rule, stage, proof, limit, or value"]
	D -- "Yes, success" --> G["Settlement, indexing, floor, or PnL display"]

Common errors

Wallet decryption failed

Cause: Vault key changed or wallet material cannot be decrypted.

Safe recovery: Stop retries. Archive the affected entry and re-import through the current vault flow after verifying the address.

Wallet already imported

Cause: The same address exists, possibly in Archived.

Safe recovery: Find the existing record, restore it when appropriate, or deliberately replace it.

Insufficient funds

Cause: Balance does not cover mint value plus fee exposure.

Safe recovery: Recalculate the whole task. Fund only the shortage plus a reasonable buffer.

Nonce too low

Cause: Another transaction already used the nonce.

Safe recovery: Refresh pending/latest nonce state. Do not force a stale pre-signed transaction.

Replacement underpriced

Cause: A transaction with the same nonce exists and the replacement fee bump is inadequate.

Safe recovery: Inspect the original transaction and use the chain/client's valid replacement rule.