assets/img/logo.svg

Empty states

What Cube tells you when a list is empty, and how to tell "nothing exists yet" from "your filters are too narrow"

Empty states

An empty list can mean very different things, and Cube distinguishes them: reading the right message immediately tells you whether you need to configure something, widen your filters, or do nothing at all because everything is fine.


The five messages

Nothing exists yet. No users, no roles, no providers, no synoptic pages: the entity has never been created. The message explains what that thing is for and, when there is a single place to start from, takes you there with a button.

No results. The items exist, but the filters or the search let none through. The message names the filters that are excluding everything, and there is always Clear filters to put them back the way they were when the page opened — free-text search included.

All clear. Zero is the right number: no active alarms. This message has a look of its own, distinct from the others, because "I have nothing to show you" and "there is nothing wrong" are opposite facts.

No access. The items exist, but none of them falls within your zones. The message tells you who to ask to get the zones you need.

Something went wrong. Reading the data failed. The message says so openly and offers to retry, instead of leaving you in front of an empty list that would look like an answer.

While a request is in flight you never see any of these messages: in their place you get a preview of the loading page, with the same shape it will have once the data arrives.

When the page loads on its own

Some pages — Limitations, Device Alert — have no search button: they populate themselves when opened. If they stay empty, the message says which link is missing: no production unit configured, no unit visible in your zones, no control device, no tags associated. These are different causes with different remedies, and the page says so instead of just showing an empty list.

Copyright © 2026