A page is empty when it should not be
Loading, empty, failed and not-computable are four different states — and an em dash is never a zero.
5 min read
Alltra deliberately keeps four states apart, because collapsing them is how a product tells you something untrue about your own trading. A page that failed to load must not look like a page with nothing in it, and a figure nobody can compute must not be printed as zero.
An em dash is not a zero. It means the figure is unknown or not computable — “$0 earned” and “we cannot work out what you earned” are different claims, and only one of them is ever true.
The four states, and how to recognise them
- Loading — the page’s own layout with each card drawn as a grey outline of itself, band for band. It is not a spinner, so nothing moves when the data lands.
- Empty — the card’s own empty state, in its own words — “No accounts yet”, “No trades match these filters”. The read succeeded and there was nothing in scope.
- Failed — a small panel in place of the page, carrying a heading, the service’s own sentence and a reference id. Home, Portfolio and Resources head it “Could not load this page” and offer a “Try again” only when retrying could actually succeed — a request that will fail identically does not get one. The Tracker heads it with the section’s name and always offers the retry.
- Not computable — an em dash in place of a value, on a card that is otherwise complete. The card stays whole rather than disappearing, so the shape of the page does not change with your data.
What to check, in order
- Name the state first — the four have nothing in common. An empty state is a question about scope; a failed panel is a question about a request.
- If empty: check the scope — the account picker, the date range, and Demo Mode. This resolves most of them.
- If empty on one card only — read what the card counts. Recent Trades holds closed trades; a table saying “No trades match these filters — clear one, or widen the date range” is telling you the filters are the cause, and it says that rather than “no trades yet” on purpose.
- If failed: read the sentence — it comes from the service and is more specific than anything the page could invent. Note the reference id before you reload, because reloading replaces it.
- If failed with no Try again — retrying cannot help — that is usually a permission or a request the service will refuse identically. The sentence says which.
- If an em dash: check whether the figure has a definition yet — several do not, and they are listed below — as an em dash, or as a card saying the figure is unavailable. Those are permanent until the definition lands, not a fault on your account.
Figures the product declines to compute today
These are not broken and they are not about your data. Each is a number the product will not invent a formula for.
- Alltra Score — a composite over six measures. It is published only when all six resolve, because a mean over four is a different statistic wearing the same name.
- Overtrading Index — no agreed formula, so nothing is published for it. The card is still on the board, in its own empty state rather than showing an em dash — headed “Index unavailable” when there were trades in the window to measure, and carrying its ordinary connect-or-import line when there were none. A filled grid with a baseline you can drag is Demo Mode.
- Consistency Score on a daily report — it is a share of profitable DAYS, so over a single day it can only read 0% or 100%. That is the reading it refuses to make.
- Portfolio Health — no formula. The gauge you may have seen filled is Demo Mode’s sample data.
- Insights, on the Journal — the tile exists and the figure has no definition anywhere in the product yet.
- The Streak card on Home — there is no per-day sign-in history to draw it from, so it shows thirty empty dots for everyone. The journaling streak in the Tracker is a real, different figure.
Pages that are genuinely not finished
- Tracker › Calendar — the month and year views do not read your trades yet. With Demo Mode off you get a real, correctly aligned, empty book. The P&L Calendar on the Performance dashboard and the day rail on Reports both read your real days.
- Tracker › Strategies — switched off. The row is visible with an “Upcoming” chip and the page does not open, because a page of invented strategies reads as your own data being wrong.
- Optimizer — the whole app is switched off in the same way.
- Budget categories — there is no way to create one yet, so the category grid stays empty and its insights panel with it. The monthly budget itself is real and settable.
When to tell us
When a failure panel appears twice on the same page after a reload. Send the reference id — it is what turns “a page broke” into a specific request we can read.
Did this article answer your question?
Something looks broken
What to include in a report so it can be diagnosed rather than guessed at.
ReadGuide last updated