Interpreting a checker timeout or unknown result

A checker that cannot produce a result has not necessarily found an invalid account. A timeout, unknown state, or processing error describes a limitation of the observation. Keep that uncertainty visible.

This guide explains what each of these states means, what to write down, and how to re-run a check on the unresolved lines, for example with the bulk account checker.

Record what the tool actually reported

Write the method, observation time, relevant nonsecret state, and whether the intended records completed. Avoid replacing the reported wording with a diagnosis such as “suspended” when the tool did not establish that.

The phone-verified aged category and the 2007/2026 Twitter accounts category use different attributes. A category label does not resolve an unknown checker result.

Match the result to the correct private record and order. Similar field shapes or display names are not enough to prove that two observations concern the same item.

Distinguish incomplete evidence from a confirmed state

Timeout

A task did not provide the expected observation within its reported process. The result alone does not establish which account condition caused the delay.

Unknown

The method did not establish the specific state being requested. Do not translate that into either a success guarantee or a confirmed failure.

Processing error

A reported error belongs to the actual method and event. Keep its nonsecret wording and avoid inventing a platform diagnosis from it.

If the output is partial, preserve which records were observed and which remain unresolved. A total shown for completed rows is not automatically a complete inventory assessment.

Check the current task, then re-run only what is unresolved

Review the current tool state and any published instructions. If a task is still processing, let it finish. If it ended with a timeout or an unknown state, you can run it again: a re-run is a new observation and may return a different result. Re-run only the unresolved lines, in smaller batches, and keep the first run's output next to the second.

The checker page describes how submissions are processed and how data is handled. It is worth a quick read before you submit again, so you know what to expect from the next run.

If the unknown results cluster on certain lines, the cause may be formatting rather than the account. Use identify-format or split-by-delimiter to confirm that each line has the expected fields and delimiter, then re-run only the corrected lines. A repeated status check will not repair a missing field or an ambiguous delimiter.

Keep differing observations together

If a later run or another method reports a state, keep it with its method and time next to the earlier uncertainty. Do not erase the earlier result, and do not treat one later observation as proof of permanent health.

Two methods may address different aspects of access or availability. Compare their actual scope rather than expecting every label to be interchangeable.

If the platform shows a login challenge or notice for an account, complete it through the official flow. A properly configured 2FA makes this smoother: the 2FA code generator produces the current code from your 2FA secret. Then run the check again.

Ask a focused question

A useful support inquiry identifies the order if relevant, checking method, time, reported state, and unresolved records. Keep passwords, session values, authenticator secrets, and full files out of ordinary messages.

If the issue concerns a delivery, say so separately and include the order reference, so support can look at the order itself instead of guessing from a checker status.

Preserve minimal private evidence and review unnecessary exports. A result file can contain more sensitive material than its status count suggests.

Frequently asked questions

Does a timeout prove that an account is invalid?

No. It is incomplete evidence from a particular process. Do not replace it with an unsupported account diagnosis.

Can unknown be treated as a successful health check?

No. Keep the uncertainty explicit rather than converting it into either success or failure.

Should I re-submit the whole file until a result appears?

No. Wait for the current task to finish, then re-run only the unresolved lines in smaller batches. This is faster and gives you a cleaner record than re-submitting everything.

What should a support question include about an unresolved check?

Use the method, time, nonsecret reported state, relevant order reference, and scope of unresolved records. Exclude access secrets and full deliveries.