Logs

The Logs tab is the screen for monitoring each individual account during a run. When you click Start, the app jumps here automatically. You get a one-row-per-account run table, a status filter, and the ability to expand any row to read its live log lines.

The empty state: "No active run"

When there is no run data, the Logs tab shows a scroll icon, the title No active run, and the prompt "Start automation to see live execution status here." This screen appears whenever the run's account list is empty — even mid-session, if the checkpoint has no accounts left.

The Status filter

Top-left is a filter dropdown (defaults to All). Each option carries a live count in parentheses.

Run status summary chips

To the right of the filter bar is a cluster of quick-count chips for the whole run (independent of the current filter): running (spinning icon), completed (green), failed (red), pending (grey). Each chip is hidden entirely when its count is 0, so the chip row changes shape as the run progresses.

The per-account run table

The main table has three columns: the expand chevron, PROFILE, and STATUS. Each row is one account, auto-updating as the run proceeds.

1. Read the PROFILE column — the email shows with the name part bold and the @domain part muted.
2. Read the STATUS column — a colored icon (grey = pending, spinner = running, green = completed, amber triangle = warning, red X = error) plus the latest status text or the result chips.
3. Let the table sort itself — running first, then failed, completed, pending.

Expand a row for the live log detail

1. Click a row — the chevron flips to ▼ and a dark log drawer opens beneath it.
2. Read each log line — every line has a time, a [module] tag and a message; colored by level (debug / info / warn / error).
3. Watch it auto-scroll — the drawer scrolls to the newest line while it's open.
4. Click the row again — to collapse it.

Module result pills (✓ / ✗ / ⚠)

When an account finishes, the STATUS column shows a result string like Login:OK | ChangeName:OK | TwoFactorAuth:!error. The app turns each piece into a compact pill with a glyph and a shortened module name, so a multi-module result reads at a glance.

• ✓ green — module succeeded (OK or OK <value>). The value lives in the hover tooltip.
• ✗ red — failure (a ! prefix or a fail keyword); the error text shows on the pill.
• ⚠ amber — needs attention / pending (a ? prefix or a keyword like appeal / submitted / pending / review / "after N days").

Module names are shortened via a display map, e.g. ChangeName → Rename, TwoFactorAuth → 2FA, ChangeRecoveryEmail → Recovery Email, and any Seed* module → Seed …. Service modules (CheckMaps, CheckYouTube) also surface state tags like Maps Suspended, Channel Terminated, or info like Local Guide Lvl:.

The three result-code prefixes

Every module result follows one of three shapes. Learn these three prefixes and you can read any STATUS line:

Diagnosing common errors

When you see a red pill or an error line, cross-check it against this list:

• reCAPTCHA — Google demands a captcha (including the camera / hand-gesture type). The app cannot solve this kind and fails fast; the account needs manual handling or should be skipped — don't hammer it with retries.
• Proxy Dead — the proxy can't connect or has died. Swap the proxy and check the IP is alive and reputable; remember that non-Google sites need an IPv6 record if your proxy egresses over IPv6.
• Phone Challenge — Google asks for phone verification. The account lands in the Verify state; it needs a real phone number to clear and can't be automated.
• Signed out — login succeeded but the session was dropped mid-flow, usually because a sudden proxy-region change made Google revoke the session. Keep each account's proxy region stable.