System Health
Schema, migration, queue, presentation and runtime health remain visible to authorised administrators.
Operational incidents should be triaged with tenant, user, screen, transaction and evidence context so support never relies on screenshots alone.
Schema, migration, queue, presentation and runtime health remain visible to authorised administrators.
Transaction IDs, audit history, scope and error details support reproducible issue investigation.
Install, upgrade, rollback and production-acceptance artefacts are maintained separately from day-to-day factory use.
Role-based quick references and factory super-user training should accompany go-live.
Connector messages, retries, reconciliation and failures remain observable instead of disappearing into background jobs.
Critical production/security incidents should follow the organisation’s configured ownership and service-level process.