Scheduler
Checking automation orchestration health.
Waiting for first summary payload.
-
Window trend appears here.
-
Repeat usage and action depth.
-
Today signup quality and tracking.
-
Signal coverage across signed-in pages.
Recommendations appear once summary data is available.
Most-viewed pages in the selected window.
Highest-impact custom actions in the selected window.
Page views and active users over time.
Custom events emitted from the app for key interactions.
Detailed page ranking.
| Page | Views | Users | Avg Eng. |
|---|
Detailed action ranking.
| Event | Count | Users |
|---|
First-touch entry capture is stored once at signup. Filters are server-backed.
-
-
-
-
| User | Joined | Entry Page | Source | Medium | Campaign | Tracking |
|---|
The admin panel edits one shared announcement config. Saving updates that shared record, disabling keeps the content but turns delivery off, and changing the ID is what makes a show-once announcement appear again for users who already dismissed it.
The panel will describe what users see once the saved config loads.
Save writes the current form into shared config. If the announcement is enabled, eligible users get that version the next time their app loads the announcement banner.
Reload Saved discards unsaved edits and reloads the last saved version. Disable saves the current form with delivery turned off. Show-once dismissals only reset when you save with a new ID.
Payload stored under global server config. Keep the ID stable while iterating; change it to re-show to dismissed users.
Low-load onboarding maturity filters plus optional manual targeting. No analytics joins or heavy runtime scoring.
Manage shared delivery defaults, reduce alert noise, and launch send-now campaigns from one tighter workspace.
Saved broadcasts inherit these channels unless you override them per send.
Operational alerts can route to admin inbox and push when subscriptions exist.
These filters apply to saved defaults and send-now broadcasts.
Push readiness, active subscriptions, and recent campaign activity show up here.
Keep the shared delivery defaults and admin alert routing compact, readable, and easy to scan.
These become the fallback channels for notification campaigns and send-now broadcasts.
Choose how operational alerts reach admins and which events are allowed to generate noise.
These filters shape both the saved notification defaults and every send-now broadcast from this tab.
Compose a send-now campaign with an inbox and/or push delivery override.
Message sent to eligible users based on the audience defaults on the left.
Quick health indicators plus the most recent notification campaigns loaded from the backend.
This tab now starts with the essentials. Recent runs, diagnostics, and dead letters load only when you open them.
| Started | Scheduler | Candidates | Cycles | Errors | Dead | Locked | Idempotent | P99 | Max |
|---|
| Created | User email | Cycle | Attempts | Review hint | Error | Action |
|---|
Use the left rail to compare tariffs by region and retailer. Select a row to inspect every interval, then load it into the editor, adjust it, and save the staged draft before publishing.
| User | Role | Automation | Joined | Actions |
|---|
Provider calls come from the daily metrics rollups only, so this chart stays on one unit system.
Cloud Monitoring request executions and failed executions are shown separately from provider traffic to avoid mixed-unit comparisons.
Share of tracked provider categories across the selected window.
Potential spikes, concentration, execution failures, and inferred overage risks. Scheduler-specific orchestration alerts stay separate.
Window totals, mix share, week-over-week change, and tracked provider issue counters.
| Provider | Window Calls | Share | Last Day | 7d Avg | Errors | Rate Limits | Trend |
|---|
Latest 14 days. Error columns stay blank when the Cloud Monitoring failure overlay is unavailable.
| Date | Provider Calls | Inverter | Amber | AEMO | Weather | Tesla EV (Wake/Command/Data) | Touches | Provider Issues | Executions | Errors |
|---|
Largest route and source contributors from the new low-cardinality API health dimensions.
What is actively probed vs passively inferred, plus whether cache misses may be pushing extra upstream traffic.