System Health
System Health gives admins a live view of the platform's status and of your organization's email, SMS, push, webhook and AI activity over the last 24 hours. Use it to spot delivery problems and to check whether an issue is on your side or the platform's before you contact support.
Access: admins only. Open System Health in the sidebar; other roles don't see it.
The page refreshes every 30 seconds. The header shows how long the platform has been running since its last restart, an Audit Log button (see Audit Log) and the overall status.
Overall status
| Status | When it's shown |
|---|---|
| healthy | None of the conditions below apply. |
| degraded | The Firestore or Realtime DB check fails, a background job's most recent run failed, or more than 10% of your organization's webhook events in the last 24 hours failed. |
| unhealthy | The PostgreSQL check fails. |
If the page shows Failed to load system health. The API may be unreachable., the platform itself isn't responding.
What each card shows
Most cards describe the platform as a whole, which every organization shares. The five activity cards at the bottom cover only your organization.
| Card | Covers | What it shows |
|---|---|---|
| API | Platform | How long the platform has been running since its last restart. |
| PostgreSQL | Platform | Whether the main database responds, how fast (ping latency), and how many of its connections are open (Pool). The bar turns yellow above 50% and red above 80%. |
| Firestore | Platform | Whether the store for configuration and contact details responds: Operational, Unreachable or Not configured. |
| Realtime DB | Platform | Whether the store for live session data responds. |
| API Requests | Platform | Requests handled since the last restart: total, 2xx (successful), 4xx (rejected, for example for invalid input or missing permissions) and 5xx (server errors). Clicking the 4xx or 5xx number copies a log-search filter for the support team. |
| Firestore Cache | Platform | How many configuration and contact records the platform currently holds in memory, by type. |
| Firestore Reads | Platform | Reads from the configuration store since the counters were last reset, with the top operations and callers. Reset starts a new measurement window for the whole platform. |
| Background Jobs | Platform | How many jobs are enabled and running, each job's last run and duration, and a status dot. Details opens Background Jobs. |
| Webhooks (last 24h) | Your organization | Events received from your email provider, your SMS provider and your funnel webhooks, plus the results of the Newsman Marketing sync: total, success, errors, the Error rate and up to five Recent errors. |
| Email (24h) | Your organization | Sent, Delivered, Pending (no delivery report yet), Bounced, Failed (rejected, marked as spam or unsubscribed) and the delivery Rate. |
| SMS (24h) | Your organization | Sent, Delivered, Failed and Clicked. |
| Push (24h) | Your organization | Devices (all registered devices, not only the last 24 hours), Sent, Failed and Opened. |
| AI Jobs (24h) | Your organization | AI generations started: Total, Completed, Running, Failed and Accepted. |
The API Requests, Firestore Cache, Firestore Reads and Background Jobs figures are held in memory and start again from zero when the platform restarts, for example after an update.
When something looks wrong
| What you see | What it means | What to do |
|---|---|---|
| PostgreSQL, Firestore or Realtime DB is unreachable or unavailable | A platform service isn't responding. Nothing in your settings causes this. | Contact support. The page updates on its own every 30 seconds. |
| A red job(s) failed recently banner in Background Jobs | The most recent run of one or more jobs failed. Jobs are shared by all organizations, so the cause may not be yours. | Open Details and check the job's history. The job runs again at its next scheduled time, or you can click Run Now. If it keeps failing, contact support. |
| Error rate in red (above 10%) | More than one in ten webhook events in the last 24 hours failed. | Click an entry under Recent errors to see its source, message and details. The source tells you where to look: newsman and newsman_marketing point to your Newsman setup in Integrations, sendsms to your SMS provider, and names starting with funnel_ to a funnel webhook. |
| Email Rate in yellow (over 80%, up to 95%) or red (80% or less) | A smaller share of the emails sent in the last 24 hours has been confirmed as delivered. | If Pending stays high while Delivered stays near zero, delivery reports aren't reaching the platform: check the Newsman webhook in Integrations. If Bounced or Failed is high, review the addresses on your contacts (see Contacts). |
| SMS Failed above zero | Your SMS provider rejected messages. | Check the SendSMS settings and your account balance with the provider. See SMS Notifications. |
| Push Failed above zero | Push notifications couldn't be delivered. | Check the Mobile Push integration. See Push Notifications & Mobile App. |
| AI Jobs Failed above zero | Some AI generations didn't finish. | Start the generation again from the page or poll list it belongs to. See Landing Pages and Polls. |
| 5xx requests climbing | The platform is returning server errors. | Contact support and include the filter copied by clicking the number. |