# A failed read, never an empty page

Source: https://docs.tightly.io/help/platform/a-failed-read
Reviewed: 2026-09-07

## The sentence

There is no one sentence: each page says in its own words that it could not read, and most say it beside a Try again. Three of them, from the Board, the Inbox and the commitment book:

> Your board could not be read just now.

> Your inbox could not be read just now.

> The commitments could not be read just now.

On Tightly Lite the Board says it of its charts:

> Your charts could not be read just now.

A commitment's room that could not read says why nothing is drawn under it:

> The commitment did not load, so nothing below would be safe to act on.

Where an address names a commitment that is not there, the read answers with one sentence, and the room prints the same words:

> No commitment with that id.

The Pre-season page, which reads one commitment by its address, says the same in its own words:

> No commitment at this address.

A page whose code did not arrive says so once, with Try again:

> This page could not be loaded.

A page that does not exist at all is the Not found page, with one door, Home:

> This link is out of date, or never existed.

## What it means

Tightly draws two different things for two different facts. A page with nothing in it says what is missing and why, in one sentence: nothing declared, nothing sold, no season waiting. A page that could not read says that, in one sentence, and draws no table under it, because a read that failed has no verdict and an empty grid would claim one. The rule behind it is the platform's: a failed request never renders as a friendly empty state, and an absence is never a zero.

A record that cannot be found is the same kind of thing. It is a failed read, never an empty position: the address named something Tightly does not hold, or no longer holds, so the page prints its sentence for that read and nothing else. The commitments' money read is the plainest case of the rule underneath: a figure it cannot compute comes back empty with a stated reason, never as a zero.

None of this is an engine that is late or stale: an engine says so with its own state word and date. And none of it is a refusal: a refusal names a rule the write met, and a failed read names no rule.

## What to do next

Press Try again where the page offers it; most failed reads last a moment. Where the sentence names a record, check the address you followed: a link from an old message, an export or another person may name a commitment that has since been retired, or one on another tenant's book. If you hold more than one tenant, switch from the account menu, which lists your Tenants by name. If the same page fails on the second try, [Something went wrong](../access/error) says what to do next; nothing in your data has changed.

## Who to ask

Ask Tightly on the page answers from this article. Where a whole page could not be loaded, its sentence carries the request's number when you point at it; give that number to whoever helps you, and they can find the same request in Tightly's logs.