Mission Control

Mission Control is where you create stopped task drafts, review them, start the intended rows, and follow their outcomes. A new installation starts with no project selected.

Before you begin

Add at least one wallet folder and one tested network. Then create or load a project from the project strip at the top of Mission Control. Projects organize task rows; creating one does not start work.

Add task drafts

Choose the entry route that matches your job:

• Collection URL: paste a supported OpenSea collection URL, load the collection, select eligible wallets, review the drafts, and create them. This is the quickest route for a normal collection.
• + Task: create one task manually. Select its provider or Custom Contract, network, wallets, price or provider detection, schedule, gas settings, and delivery route.
• Import CSV: import a reviewed batch containing wallet name or address, contract, hex data, and price. Use this only for trusted custom-call data.

New drafts remain stopped. If a draft is missing a wallet, network, contract, or other required value, edit the row and resolve the displayed blocker before starting it.

Review and start

1. Confirm the project and the exact task rows in view.
2. Review each row's wallet, network, task scope, price or value, schedule, gas limits, and route.
3. Start one row with its Start action. For a batch, select the intended rows and use the Selected control. Use All only when every row in the project has been reviewed.
4. Use Stop to request that a running task stop before another attempt is made.

The activity console is collapsed by default. Expand it when you need the sanitized reason for a blocked or failed row.

Read the outcome

• A final success means Sthang observed successful inclusion.
• A final failure or reverted result means the attempt completed without success.
• submitted, visibility pending, receipt pending, or another pending/unknown result is unresolved—not a failure and not permission to retry.
• Stopped or Expired means no further work should be assumed for that task, but any earlier submission still needs independent confirmation if its outcome was ambiguous.

Mission Control is ready for the next task when the intended rows have a clear final state and no protected work is active. Before installing an update, stop active work and wait for Sthang to report that it is idle; the updater never stops financial work automatically.