Start All & pacing

Start a group#

1. 1

   Select a group, or tick the rows you want

   If you tick rows, only those start. With no group selected and no rows ticked, every task in every group starts.
2. 2

   Click the play button

   It sits in the task toolbar, and its tooltip reads Start. You can also right-click a group card and choose Start All. That always starts the whole group.

• Tasks start in the order you created them. That matches the rows on screen only when the sort is set to Created.
• Start All skips tasks that are already running or already finished.
• Finished includes failures, such as GEN FAILED, ADD SMS FAILED, LOGIN BLOCKED (PX), NO LOGIN CODE and SMS SOLD OUT. To run these again, press the stop button (the square icon) first. It turns them into STOPPED, and Start All picks those up.
• It skips a gen task that already minted an account, or whose address already had one. That address is not signed up a second time.
• It clears an earlier stop. Each task gets a fresh auto-retry budget with no leftover backoff, the same as pressing play on a single row.
• Tasks over a cap wait at QUEUED and start on their own as slots free up.
• After you quit or restart the app, nothing resumes on its own. Every task comes back as IDLE, except rows on ACCOUNT GENNED, SMS VERIFIED or ALREADY GENNED. Press Start All to run them again.

The stop button is the square icon next to play. It leaves rows that show a result alone. These are ACCOUNT GENNED, SMS VERIFIED and ALREADY GENNED. To stop those too, click the caret beside it (More stop options) and choose Stop Genned Too. This clears the group back to a state Start All picks up in full.

How fast tasks start#

Start All works through the tasks quickly, up to 200 a second. There is no setting for this rate.

A task Start All has not reached yet shows IDLE, not QUEUED. On a big group this can last a few seconds. If it looks like nothing happened, check the blue arc counter on the group card. It counts running tasks, and it moves first.

Tasks that log in first#

Add sms tasks log in to each account before they attach a number. Each task logs in on its own when it runs. You cannot log accounts in ahead of time, and there is no setting for how many log in at once.

If you start many Add sms tasks for accounts with no saved session, a notice may appear. It says the tasks need a fresh login and tells you to pre-login with Log In All. There is no Log In All button. The tasks log in as they run, so you can ignore the notice.

Caps#

Each module has a cap on how many of its tasks run at once. AETHER sets the caps, and you cannot change them.

• A cap counts tasks across all your groups. Two groups of the same module share the same slots. Walmart CA and Walmart US tasks count toward the same Walmart slots.
• Tasks over a cap show QUEUED. This is not an error, and it is not a queue you set up. They start on their own as slots free up.
• Hover the QUEUED status on a row to see why it waits. For example: waiting for a free Walmart slot — that module is at its cap (30).
• The tooltip can also say the machine ceiling is full, or that gen tasks share one ceiling across all groups. Then tasks in other groups or modules hold the slots.

Start small first#

You cannot change the start rate or the caps. What you choose is how many tasks you start, and when.

Starting a big group does not make it finish faster. For most modules, only as many tasks as the cap allows run at once. The rest wait at QUEUED.

For a good start:

• Tick a few rows and start those first.
• Wait for their results before you start the rest of the group.

Watch the statuses on the first few rows before you go wider. They are the quickest way to see whether tasks are getting through or burning through your supply.