Jobs

Fund, Collect, Reclaim rent, and transfers by relay or through the exchange all run as jobs: plans that a worker on the server carries out one transaction at a time. Start one from your phone, close the tab, and it keeps going. You can watch it live, pause it, or stop it, and so can your teammates.

Review, then Start

1. 1
   Fill in the form

   Source, wallets, amount, route and pace. Nothing is sent from the form, and changing your mind costs nothing.

2. 2
   Review

   Review builds the plan on the server and saves it as a draft: the total, how many wallets (and how many already have enough), what each gets, the route, the network fees and how many transactions they cover, the source's balance before and after, and roughly how long it takes.

3. 3
   Start

   Start · N transactions hands the draft to the worker. The dialog then follows the job and offers Open job; you can also just close it. A draft you never start expires after 15 minutes, and a workspace runs up to 10 jobs at once.

Pace

The pace decides how quickly the transactions go out. Fast is right for most moves; spreading them out makes a batch look less like one batch on chain.

As fast as possible3 at a time

Up to N wallets Per transaction (20 for a direct fund, 9 for a collect), three transactions in flight at once. Relay and Private move one wallet per transaction, three at a time.

Spread outpause up to an hour

One transaction at a time, with a random pause between them in the range you set (Pause from … to, in seconds, up to an hour).

Statuses

Waitingqueued

Started, not picked up by the worker yet.

Runninglive

Sending. The job page counts down the transactions and estimates the time left.

Pausedneeds you, or you asked

Holds before its next transaction. It says why; fix that and press Resume.

Cancellingwinding down

Transactions already sent still settle; nothing new starts.

Done · Cancelled · Stoppedfinished

Done ran to the end. Cancelled was cancelled by someone. Stopped hit something it can't go on from, and says what.

The job page

Jobs in the main menu (with a count while some run) lists jobs under Running now and Earlier. A job's page shows:

• Progress. The SOL sent so far of the total, About N left while it runs, and a bar of confirmed, skipped and failed transactions.
• Controls. Pause and Resume; Retry N failed and Skip failed when some transactions failed; Cancel job, which asks Cancel the rest? before Yes, cancel. The person who started the job, owners and admins can use them.
• Details. From or into which wallet, the route, what each wallet keeps (Leaves), network fees paid and planned, the pace, who started it, and when it started and finished.
• Transactions. Each one with its wallets, its amount and a link to Solscan, and a line while it's in flight, such as Sent, waiting for the network or Sent (try 2), waiting for the network.
• Journal. Every event in order: picked up, each transaction signed and confirmed, pauses with their reason, retries.

When a job finishes, pauses on its own or stops, everyone in the workspace who has the app open gets a toast with a button to open it.

Pauses instead of failures

A job that runs into trouble pauses and tells you why, rather than failing and leaving a half done batch to sort out by hand. It pauses when:

• someone pressed Pause;
• the source doesn't have enough SOL for the next transaction;
• a transaction failed;
• its creator lost access to the workspace;
• the Solana RPC kept failing.

Top up the source, check the failed step, then Resume. A job paused because its creator left shows Take over and resume to owners and admins: it then runs the rest on their behalf.

Saved before it's sent

One step of a job is one transaction, and each goes through the same careful path, so a slow network or a crash never sends money twice:

1. The transaction is built, checked and simulated against the chain right before it goes.
2. It's signed and saved on the server first, then sent.
3. If the answer gets lost, the same signed transaction is sent again, and the worker keeps asking the chain until it's confirmed or has failed.
4. Only once the old one provably can't land anymore does it build a new one, shown as the next try. Three signed attempts at most; after that the step fails and the job pauses.

The worker

Jobs run on a background worker, not in your browser. The Jobs page shows its state as a pill: Worker online, Worker offline or Worker not running. While it's away, jobs wait and carry on when it's back; nothing is lost.

What jobs don't cover

A direct transfer from one wallet goes at once, without a job, and single transfers are limited to 20 a minute per person. Warmups have their own run page with the same safety rules; see Warmup. Launches and trades run on the server too, in the coin's panel.