Status

Operational confidence starts with clear system health.

Use this status overview as the entry point for understanding whether the public product surface and reminder operations are behaving as expected.

Public application health

The public frontend, auth surfaces, and workspace routes should be readable, current, and aligned with the latest successful build and deployment state.

Frontend

  • Frontend availability
  • Asset delivery integrity
  • Public route readiness

Reminder operations health

Status should also reflect whether delivery pathways, fallback routes, and retry flows remain operational enough for trustable recurring reminder support.

Operations

  • Reminder queue state
  • Channel fallback readiness
  • Failure visibility

Need deeper product context around status signals?

Review the feature and API pages to understand how these operational states map back to real user workflows.