Gmail live/die check
The Check button (a blue button with a magnifier icon, sitting after a divider to the right of Export) runs a live status check against Gmail and updates each account's Status Gmail column. The label changes by scope: Check All when no rows are ticked, or Check (N) when you've ticked N accounts.
Prerequisite: the Gmail Checker API key
This feature calls the check-gmail.live service, so you must enter its API key first. Go to the Automation → Other tab and paste the key into the Gmail Checker field. Without a key, the check will fail.
You only need to enter the API key once; it's saved for later runs. If a check always reports ✗ Check failed, go back to Automation → Other and verify the key is correct and still has quota.
Statuses it returns
Results surface as badges in the Status Gmail column:
| Status | Meaning |
|---|---|
| LIVE | The account is alive and signs in normally. |
| Verify | The account demands extra verification (a challenge) — handle it before use. |
| Disabled | The account is disabled/locked — effectively dead. |
Fast Check
The Fast Check option performs a quicker check, trading depth for speed when you need to sweep a large batch in a short time. Turn it on when you just want a rough LIVE/Disabled filter across many accounts; turn it off when you need the most reliable result per account.
Steps to run a check
- (Optional) Select accounts — tick specific accounts to check only those; the label becomes Check (N). Leave none checked to check all (Check All).
- Click the Check button — it switches to a spinning Checking... state while it runs.
- Wait — the table auto-refreshes as results arrive; progress is polled every 2 seconds.
- Read the results — when finished, a green ✓ Check completed! message appears for a few seconds and the Status Gmail badges update.
- If only part of the batch got through — instead of the green message, a warning stays up for about 12 seconds: ⚠ Checked {ok}/{total}. {N} accounts could not be checked (reason) — their status was left unchanged.
The Check button is disabled while a check is running and when there are zero accounts in the table. There is a hard safety timeout of 120 seconds: after that the spinner is cleared and the table refreshed even if the backend hasn't reported done — so a very large batch may visibly stop "Checking..." before it truly finishes. On a request failure it shows ✗ Check failed.
What does "their status was left unchanged" mean? The accounts that could not be reached keep whatever status they already had — they are NOT marked dead or errored. The usual causes are a spent quota on the checker key or a network drop mid-run. Fix the cause, tick just those accounts, and press Check again.