Troubleshooting

A task will not start#

If a mode is missing something it needs, AETHER does not create the task. A toast shows the reason.

AETHER checks the requirements in a fixed order and reports only the first one missing. Fix them in the order below.

Some gaps only show once the task starts. A Target gen task stops at STOPPED when no IMAP inbox is saved under Settings, IMAP. Its log says Target needs an IMAP inbox. An AYCD inbox does not count for Target. An Amazon gen task with no inbox ends at NO OTP INBOX ATTACHED. An add-SMS task with no SMS provider saved under Settings, SMS stops at STOPPED.

A task that sits at QUEUED was created and is waiting for a slot. QUEUED is a progress status. Most modules run up to 5 tasks at once, and Walmart CA runs up to 30. The rest wait their turn. Hover the status to see which module the task is waiting for. You cannot change these caps. See Start All & pacing for how tasks are admitted.

Everything fails at once#

When a whole group fails in the first few seconds, the cause is far more often your proxies or inbox than the store. Check the proxy list first, then whether an inbox is missing, then the store.

A dead proxy looks exactly like a block. When a proxy never connects, the task gets no response, so it rotates and tries again. That fills the run with ROTATING PROXY and BLOCKED BY AKAMAI, even though no request reached the store.

A proxy plan that has used up its data refuses every connection before any request reaches the store. The limit is on the whole plan, so every proxy on the list fails and rotating cannot help. AETHER ends the task at OUT OF PROXY DATA instead of retrying.

Tell a dead proxy from a block#

1. 1

   Open Proxies and select the list the failing tasks use

   Pick the exact list named on the task.
2. 2

   Set Test against to the store those tasks are hitting

   Proxy logins are locked per store. A list that works on Walmart does not automatically work on Pokémon Center.
3. 3

   Click Test all, or Test on one row

   Results appear in the Status column as they arrive. Click Stop to end the test early.

A row shows — before it is tested and testing… while the test runs. Hover any result to see the full sentence behind it.

For list formats and where lists are saved, see Proxies. Two other causes look the same. Rule them out first.

• A task with no proxy list, or an empty one, still runs. It goes straight from this computer's IP, the same as Localhost — this PC's IP, no proxy. A gen task started without proxies warns in the visible log that Walmart will likely block it.
• NO OTP INBOX ATTACHED means the mode needs to read email and has no inbox to read. See the next section.

No verification code arrives#

The task waits at WAITING FOR CODE, then ends at NO OTP RECEIVED. Check these in order. Walmart CA gen needs no email code, so this section does not apply to it.

1. 1

   Check that the task has an inbox

   NO OTP INBOX ATTACHED means the task never had an inbox to read. NO OTP RECEIVED means it read the inbox and no code came. Target gen reads only an IMAP inbox saved under Settings, IMAP. With none saved, the task stops at STOPPED. An AYCD inbox on the task does not count.
2. 2

   Test the inbox

   Test connects, logs in, opens INBOX and reports the result. It does not count verification codes, because a healthy new inbox has none.
3. 3

   Check how many connections the run opens

   IMAP servers limit how many connections one account can hold at once. Past that limit, tasks time out and show NO OTP RECEIVED, even when the password is right.

A large run opens many connections, on top of the one AETHER's reader already holds. If a run works at five tasks and fails at two hundred, it is over the connection limit. The password is not the problem. Spread the run across more inboxes, or start fewer tasks at a time.

See OTP inboxes for inbox setup. Add-SMS also signs in with an emailed code. See Walmart US for that mode.

The licence gate appears#

• Cannot reach the license server. or Could not verify your license right now. means the check could not be made. Nothing was decided and your key is kept. Click Activate again.
• A message that names a reason is a real refusal. Examples are a membership that ended, an expiry, or a key in use on another computer. Deal with that reason.

For the full table, see Activate your licence.

A mode is missing from the picker#

The modes in the picker depend on the group's retailer and region. If the mode you want is not there, that retailer and region do not support it. See Modules for what each retailer can do.

Find the logs#

In the app

Click a task row to open the Task Logs — task <id> drawer. It refreshes on its own while open, faster than the task table. Copy to Clipboard copies the lines currently shown.

The drawer shows status changes, newest first, in a Time and a Message column. Each line is tinted by whether that status was progress, a warning or a failure. Every change is shown, so a loop such as solving, blocked, rotating, solving stays visible.

The drawer also shows AETHER's own warnings in the failure colour, as a short headline such as NO PROXIES IN THE SELECTED LIST. Hover the line to read the full sentence.

Raw engine output never reaches the drawer. It stays in the log file. The drawer is for reading, and the file is what you hand over.

On disk

The run folder is .ui-runs, next to AETHER's installed files. If AETHER cannot write there, for example on a mapped drive or a read-only or sync-locked folder, it uses ui-runs inside your data folder. Only then does it print one line, naming the folder it used instead. Your data folder is ~/.aether by default (see Install).

Export a log bundle

In Settings, go to Diagnostics, Backend logs and click Export. This bundles the last 20 MB of aether.log, the crash log, a summary of every task and the logs of up to 60 tasks into one encrypted .aetherlog file. Your system's save dialog asks where to save it.

The file is encrypted to a key that is not on your machine, so it is safe to pass along. It tells far more than a screenshot of a task row.