Two places tell the truth first: the status strip under the Monitor wall (hover it), and the Jobs tab. On the torii side, the Accounts table’s Status / Health columns.

​
The wall is empty and the strip says no torii token

Your Doxaform user has no torii key bound. Keys are per user — an admin’s key does not cover you. → Connect torii.

​
The strip says auth_required or 401

The bound key was revoked or mistyped. Mint a new key in the torii console, save it under Settings → Keys & services, and force a crawl with ↻.

​
A source shows blocked

Hover the badge. The code tells you which kind of “no” it is:
A bot check or a risk-control page. Not a login problem: torii backs off automatically and the next crawl usually passes. If it persists for hours, the platform is throttling that account — add a second account for the platform in torii, or lengthen the signal’s interval.
torii paces every account; a burst of requests widened the gap. Nothing to do but wait; consider a longer interval or a per-platform floor under Settings → Deployment.
The only one of the three that needs you. In the torii console, the account’s row is dead — Re-login it. The tooltip on the Doxaform badge says the same thing: session dead since … — re-login it in torii. Once the row is ready, the next crawl is live.
On a multi-account posts source, the other seven accounts delivered. The wall is live; only part of the source was throttled.

​
A source shows error — sources returning nothing / could not resolve ref

The source’s query is wrong for the platform: a wrong id, a handle where an id is expected, or a share code the platform no longer resolves. Open the ⚙ editor and check the row. Since torii resolves share codes, v.douyin.com/<code> style refs are accepted; a plain profile URL is not.

​
The wall is empty but every source is live / empty

That is an honest empty: the query has nothing new right now. Check the signal’s filters (a narrow fresh window or a high min likes hides everything), and remember retention — with a window set, old clips age out.

​
The signal cards are missing after a reload

The rail is fed live. If it is empty a few seconds after loading:
  1. Reload once — a reload that raced a server restart can render an empty rail.
  2. Check whether it is the tunnel or the console: open the console on its local address. If local is fine and the tunnel is slow or 502, the tunnel is the problem, not Doxaform.
  3. Sign out and back in. Sessions are host-locked (__Host- cookie) so an old cookie from another console on the same domain can no longer shadow yours — if it ever did in the past, one fresh login clears it.

​
Hovering a card shows nothing / the chip spins forever

  • YouTube cards have no preview yet; you get the cover.
  • A chip means the preview is still rendering; it usually completes within seconds. Previews are rendered at crawl time, so this is rare and only on brand-new cards.
  • No chip and no video on an old card: the clip predates previews and its source address has expired. It will age out with retention; purge it if you want it gone now.

​
A download failed

Open the artifact; the error names the cause: Renders run one at a time by default; a big batch is slow, not broken — watch it in Jobs.

​
The console is slow or will not load

First tell tunnel from local: if the local address answers instantly and the public one does not, the tunnel is the problem — tell your operator. If both are slow, check Jobs for a stuck flood of jobs and the torii console’s Activity tab.

​
I cannot sign in

  • Wrong password: ask an admin to reset it (Users tab).
  • Signed in elsewhere: your account’s multi-login policy is single-session; revoke the other session under Settings → Sign-in & security, or ask an admin.
  • Repeated failures lock the username for a minute before the KDF is even run — wait and try again.

​
torii console: an account is dead after a restart

Sessions are kept on disk and normally survive; a dead row means the platform invalidated it. Re-login from the row menu. If the QR expires before you scan, close the view and start again — a fresh QR is issued every time.

​
torii console: the live browser shows a captcha or an SMS prompt

Solve it in the live view — you are driving torii’s browser. That is exactly what the live view is for; do not try to log the account in from your own browser, the session would land in the wrong place.

​
Where the logs are

Ask your operator: Doxaform’s server log names every crawl with its source, outcome and item count; torii’s Activity tab lists every task and request with its status and duration.