Operations
System Health
Check allocation and notification processing, saved receipt review counts and recent failures.
Use your signed-in school SMC or administrator session. Open Roster to sign in.
Status updates only when you open this page, refresh it or request a review preview. Cloudflare’s Worker metrics and logs remain the source for CPU usage and execution limits.
Prepare timetable migration · Administrator only; Google stays authoritative.
Scheduled and background work
Successful notification processing does not confirm message delivery. The sent counter records provider acceptance; confirmed delivery must be checked in the existing delivery records.
Idle means there was no work due. Skipped means the task did not run. Neither counts as a successful completed job. Identical idle and skipped reports are recorded at most once every five minutes.
| Job | Latest outcome | Last successful processing | Diagnostic |
|---|
Pending work
Background queue
Retry is available for parked background jobs. It preserves existing delivery safeguards and does not reset uncertain message deliveries.
Timetable cache
Preparation times show when packages were built. Each read verifies the relevant source version and permissions before reuse.
R2 cleanup
Colleague email review
Admin only. Check with the recipient before marking an uncertain email reviewed. This records your review, preserves the original provider outcome and sends no email. Pending and blocked messages are separate work.
Recent failure history
These are retained past processing outcomes, not cancellable queue items. A later successful run or administrator review does not erase this history. Check the latest outcome and current review counts to see what still needs attention.
Use the time, safe code and available trace reference to find the matching Cloudflare Worker log. The Worker trace identifies the matching Worker log. The backend reference is a separate diagnosticId; backendVersion, failureStage and operation identify the backend build and failed action when available. These safe references are retained with the processing outcome. The health summary contains no staff details or message contents.
Recovery checkpoints
A checkpoint records a native D1 Time Travel bookmark. Restoration remains an operator action following the recovery guide; it affects the shared database and does not restore R2 or reverse messages already sent.