What users see today
The dashboard's Recent Activity section reads tenant-scoped audit records. It is a query view, not a guaranteed live stream. An internal WebSocket feed and safe activity component exist, but operational event writers are not yet connected to that feed.
When a feed connection is interrupted
For published feed events, a reconnecting browser uses its last event sequence to request missed events. If a sequence gap remains, its activity component labels updates as delayed while catch-up retries. This does not turn an unwired event source into a live dashboard.
When feed access changes
The feed server periodically rechecks an active credential. Invalid or revoked access ends the connection. A temporary authentication-store outage is retryable; revoked browser sessions require signing in again.
What still needs operational proof
Source tests cover delivery and recovery behavior. Production throughput, long-duration soak, and restore objectives require separate measured evidence before an availability or recovery guarantee can be made.
Frequently Asked Questions
Does the dashboard stream operational events today?
No. Recent Activity queries audit records. The internal feed has replay and connection handling, but no production operational writer publishes into it yet.
What happens after a brief feed interruption?
For events that were published, the browser requests missed records from the durable sequence API. A delayed status means catch-up is still incomplete.
Does this page prove a production availability target?
No. An availability or recovery target needs measured load, outage, and restore evidence.
Topics
Ready to try it?
Evaluate the workflow with your own approved data, integrations, review gates, and success criteria.
Explore the platform