Skip to main content
A partial or unavailable state is an honest result about source coverage. It should change how you report the panel, not force you to discard every neighboring observation.

Start with the state sentence

Read the panel title, description, state, caveat, and source before reading any number. The state explains what the values can support.

Partial results

Partial means part of the requested reading is usable. Examples:
  • one PageSpeed device completed while the other is still running;
  • Search Console returned query rows but not headline totals;
  • a provider returned totals but limited a high-cardinality breakdown;
  • a crawl read some pages but could not reach others.
Use the readable portion and keep the caveat beside it. Do not fill missing sections with estimates unless you clearly label a separate, human-created estimate outside Alesta.

Unavailable results

Unavailable means the source or operation did not produce usable evidence. Common causes include:
  • insufficient eligible real-user samples;
  • blocked or unreachable pages;
  • provider coverage limits;
  • expired authorization;
  • a service that is not deployed in the current environment;
  • an upstream request that failed.
An unavailable panel is not a low score and not a zero.

Not measured

Not measured means the current run did not ask that question or lacked the required source. This can be expected for a free public baseline when a deeper provider-backed measurement did not run. For example, no observed AI-mention run means Alesta should not claim zero mentions.

Locked and coming soon

  • Locked is a plan-access state. The provider has not necessarily been asked.
  • Coming soon is a product-availability state. Upgrading or connecting a provider will not activate it.
Keep both separate from unavailable data.

Reporting template

Use a structure like this:
Search Console query rows were available for the last 30 days, but headline totals were not readable for the same window. The listed queries are usable as partial evidence; no total-click conclusion is reported.
Avoid:
Search clicks were zero.

Decide what to do next

1

Check whether work is still running

Review the global progress indicator and Logs before treating the panel as terminal.
2

Read the reason

Identify whether the boundary is plan, connection, provider, source coverage, or a transient failure.
3

Use the valid portion

Preserve the exact source, window, and caveat for any readable data.
4

Take the narrow next step

Connect, select, reconnect, retry, upgrade, or provide business context only when the reason calls for it.

References