System-Wide Status
Check the live health of REDENES servers and services, grouped and color-coded by state.
The System-Wide Status screen reports the health of the servers and services behind REDENES. Items are organized into groups you expand, and a color-coded count at the top tells you at a glance how many systems are online, offline or reporting an error. Each group carries its own counts too, so you can narrow down a problem without opening everything.
Overview
| Status | Color | Meaning |
|---|---|---|
| Online | 🟢 Green | The system is operating normally |
| Offline | ⚪ Gray | The system is offline |
| Error | 🔴 Red | The system is reporting an error |
Each server row shows four pieces of information plus a status dot.
| Field | What it shows |
|---|---|
| Server name | The server's own name |
| Location | Where it runs |
| Environment | Which environment it belongs to |
| Status dot | Gray, green or red per the table above |
| Last outage | The date of the last failed check, or NONE |
Groups are listed alphabetically by name, and servers inside each group are listed alphabetically too, so the screen reads the same way every time.
Getting Here
- Open the Account tab.
- Open App Settings.
- Choose System-Wide Status.
Depending on your build, this row may open the public REDENES status site in an in-app browser instead of the grouped list described here. Both show the same information; the site version has its own layout and does not use your date format.
Loading and Empty States
| State | What you see |
|---|---|
| No connection | An "internet not available" message appears immediately and nothing loads |
| Loading | A spinner covers the screen while the status is requested |
| Loaded | The counts fill in and every group appears, all collapsed |
| Request failed | The spinner clears and an alert shows the server's error text |
| Request timed out | The app retries once automatically, then offers a timeout alert with Try Again |
Every group starts collapsed, so a freshly opened screen shows only headers and counts.
This screen needs a live connection and nothing is cached. If REDENES itself is unreachable you will get the "internet not available" message or an error rather than a page of red dots — being unable to load this screen is itself a signal.
Reading the Counts
- Look at the count row at the top for totals across every system.
- The three numbers are gray, green and red, in that order: offline, online, error.
- Each group header repeats the same three counts for just that group.
| Count position | Meaning |
|---|---|
| First, gray | Systems currently offline |
| Second, green | Systems currently online |
| Third, red | Systems reporting an error |
A group whose counts are all zeros contains no reporting servers.
Scan the group headers rather than opening everything. Any group with a non-zero red or gray count is where to look; the rest can stay closed.
Expanding a Group
- Tap a group header. The arrow beside the name changes to point down and the group's servers appear beneath it.
- Each row shows the server's name, location, environment, status dot and last outage date.
- Tap the header again to collapse the group; the arrow points right once more.
- More than one group can be open at a time.
What the Three States Actually Tell You
The difference between gray and red matters when you are deciding what to do.
| State | Likely meaning | What to expect in the app |
|---|---|---|
| Online | The service answered its check normally | Normal behavior. A problem you are seeing is probably local |
| Offline | The service is not answering at all | Features that depend on it will fail outright, often with an error |
| Error | The service answered but reported a fault | Features may half-work — slow, incomplete, or failing intermittently |
Error is the state worth reporting. Offline is usually already known and being worked on; an intermittent error is the kind of thing that benefits from you saying which feature misbehaved and when.
Working Out Whether It Is You
Use this screen together with the status panel on App Settings to place the fault.
| This screen | Your internet status | Most likely cause |
|---|---|---|
| Will not load at all | Not Connected | Your own connection |
| Will not load | Connected to something | The status service itself, or a wider outage |
| Loads, all green | Connected | Your device, your settings, or your app version |
| Loads, something red or gray | Connected | A REDENES service. Note which one |
Reading the Last Outage
| Value | Meaning |
|---|---|
| NONE | No failed check has ever been recorded for this server |
| A date | When the last failed check happened, in your own date format |
With no date format stored, the date falls back to a plain year-month-day form.
How This Connects
- Where the data comes from. A single live request to the REDENES status service each time the screen opens. Nothing is stored on the device, so every visit is current — and every visit needs a connection.
- What updates it. The monitoring behind the service. There is no refresh control on this screen; leave and come back to get a newer reading.
- Date formatting. Outage dates use the format you chose on App Defaults. Change it there and it applies here the next time you open the screen.
- When to use it. Before raising a ticket. If a service you rely on shows red or gray here, the problem is not your device or your settings — mention what you saw when you open a ticket on Support.
- Your own connection. This screen reports the servers, not your device. Your own internet, watch and CarPlay status are shown at the top of App Settings.
- Not device status. For the phones and tablets signed in to your agency, use Devices.
- Offline and reconnect. Unusable offline by design. Reconnect and reopen the screen; there is no queue and no stale copy to read.
Troubleshooting
| If this happens | What to do |
|---|---|
| An "internet not available" message appears at once | This screen needs a connection and caches nothing. Reconnect and reopen it. |
| The spinner clears with an error alert | The status request failed. Try again shortly; if it keeps failing, the status service itself may be affected. |
| A timeout alert offers Try Again | The request timed out after an automatic retry. Tap Try Again, or come back when your connection is more stable. |
| The screen is blank with no groups | The request returned nothing usable. Leave and reopen the screen. |
| A group shows counts but no rows when tapped | Tap the header again — the arrow shows whether the group is open. |
| Every count is zero | No servers are reporting. Reopen the screen for a fresh reading. |
| Outage dates look wrong | They use your format from App Defaults. With no format set, a plain year-month-day form is used. |
| A server shows NONE for its outage but a red dot | NONE means no recorded failed check. The red dot is the current state; both can be true at once. |
| Something in the app is broken but everything here is green | The fault is more likely local. Check your connection at the top of App Settings, then open a ticket on Support. |
| The screen opened a web page instead of the list | Your build routes this row to the public status site. The same information is there. |
Related Pages
⬅️ Previous: Home Widgets | Next: Support ➡️