Certificate Expiry Check Edge Function

Medium complexity with three upstream dependencies: certification-expiry-repository, expiry-notification-orchestrator, and mentor-visibility-suppressor—all of which must be complete and tested before end-to-end integration of this edge function. The cron schedule must be configured in Supabase project settings and verified in both staging and production environments. Key delivery risks include: cron misconfiguration leading to missed daily runs, edge function execution timeouts if the mentor dataset is large (Supabase edge functions have a default timeout), and failure isolation if one dependency throws—the function must not abort the entire batch on a single record failure. Observability is critical: logExecutionResult must produce structured logs consumable by the monitoring stack.

A manual trigger endpoint (handler via HTTP POST) should be included to support operational testing without waiting for the cron window.

Implemented as a Supabase Edge Function (Deno runtime) registered on a daily cron trigger. The handler entry point validates the request (cron invocation vs. manual HTTP trigger), then calls runDailyExpiryCheck, which invokes certificationExpiryRepository.getUpcomingExpirations for each configured threshold window (60/30/7 days) and getExpiredMentors. Results are passed to processExpirationBatch, which iterates records and calls expiryNotificationOrchestrator for notification dispatch and mentorVisibilitySuppressor for expired records.

Each record is processed in a try/catch to ensure one failure does not abort the batch. logExecutionResult writes a structured JSON log including batch size, success count, failure count, and per-failure error details. The function should be idempotent: repeated runs on the same day should not produce duplicate notifications, relying on notificationRecordRepository's threshold deduplication. Environment variables must supply the Supabase service role key and any configurable threshold values.