Activity

Every Session a phone runs is recorded and uploaded, so the browser can answer whether a rack actually works.

What a Session records#

Which Account and Platform, which phone and Mac, when it started and how long it ran, what it did, and why it stopped.

An Action ends in exactly one of three ways: Succeeded, Failed, or Unrecognized. There is no fourth.

Unrecognized is its own outcome on purpose. It means tame did not know what was on screen, which is a different problem from an action that was attempted and went wrong, and the two need different responses from you.

Recorded carefully#

• A Session you stopped by hand is not a failure. A failure rate inflated by your own decisions is a number nobody can act on.
• A Session on a phone that is gone is still shown. History does not disappear when hardware does.
• A Session that ended before it started is kept at zero length. Clocks disagree occasionally, and dropping it hides that it happened.
• One bad row does not lose the batch.
• The same batch sent twice is recorded once, so a Mac that retries does not double count.

What is not recorded#

Your content. What an Account posted is never written to a log, and neither is anything else a Client owns.

Phones are identified to us by a pseudonym rather than their hardware identifier, so the same phone in two Workspaces cannot be correlated.

Reading a failure#

Every failure carries a plain language cause next to a stable code that stays in the logs. You should never see the code. If you do, that is a defect.