System status

There is no public status page today. This is how to tell an outage from an honest empty state, and how to report one.

What you'll learn

• How to tell a fault from a working empty state
• What a partial degradation looks like in this product
• How to report something, and what to include

First, rule out the honest empties

This product deliberately reports absence rather than inventing a number, so several working states look like faults:

See when a number is missing.

What an actual fault looks like

• Nothing new for more than a full check cycle across every surface, with coverage available.
• The assistant failing to answer rather than answering that it found nothing.
• A connector reporting broken when nothing changed on your side.
• Reports not arriving on a schedule that previously ran.

Partial degradation

An engine can be unavailable while the rest of the platform is fine. When a surface returns nothing usable, it is reported as an exclusion with its staleness rather than as a zero, so a single-engine outage shows up as an exclusion that does not clear.

That is the pattern to watch for: an exclusion on one surface that persists across several cycles while other surfaces report normally.

Reporting it

Email support@outercite.com with:

1. The workspace name.
2. What you expected and what you saw, with a screenshot of the panel.
3. When you last saw it working.
4. For a data question, the window shown in the footer under the answer.

Planned work

Anything that changes behaviour is published on the changelog. If a figure has moved and nothing is broken, that is the first place to look.

Try this in Outercite

Before reporting a data problem, ask the assistant the question again and read the trace. It tells you what it checked and how much of it there was, which distinguishes "nothing was found" from "nothing ran".

Related