Implement expiry check edge function — cron trigger and query
epic-certificate-expiry-notifications-orchestration-services-task-014 — Create the Supabase Edge Function that runs on the daily cron schedule. The function queries the certification expiry repository for all mentors with certificates expiring within 60 days or already lapsed, partitions results by threshold tier, and passes each partition to the downstream services: orchestrator for notification dispatch and visibility suppressor for lapsed mentors.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 3 - 413 tasks
Can start after Tier 2 completes
Implementation Notes
Structure the function as a pipeline: `query → partition → dispatch`. Keep each stage in a separate async function to make the flow readable and independently testable. The tier boundary comparisons should use UTC timestamps exclusively — never local time — since Supabase runs in UTC. Use `supabase.from('certification').select(...)` with `.lte('expires_at', sixtyDayBoundary)` to retrieve all candidates in a single query, then partition in JavaScript.
Define the tier boundaries as named constants at the top of the file (`LAPSED_BOUNDARY`, `SEVEN_DAY_BOUNDARY`, etc.) so they are easy to adjust. For dispatching to downstream services, use Supabase's `functions.invoke` method rather than raw `fetch` to benefit from automatic auth header injection.
Testing Requirements
Integration tests using Deno test runner with a mocked Supabase client. Required scenarios: (1) certifications spread across all four tiers are correctly partitioned — verify counts match; (2) lapsed certifications trigger calls to BOTH orchestrator and visibility suppressor; (3) non-lapsed tiers trigger orchestrator call only; (4) empty database result returns 200 with all-zero counts; (5) downstream orchestrator failure for one tier does not prevent other tiers from being processed; (6) function returns HTTP 200 with error summary when partial failures occur. Additionally write a manual smoke-test checklist for staging: verify pg_cron fires, check execution log table, confirm notification records created.
If the daily edge function runs more than once in a 24-hour window due to a Supabase scheduling anomaly or manual re-trigger, the orchestrator could dispatch duplicate push notifications to the same mentor and coordinator for the same threshold, eroding user trust.
Mitigation & Contingency
Mitigation: Implement idempotency at the notification record level using a unique constraint on (mentor_id, threshold_days, certification_id). The orchestrator checks for an existing record before dispatching. Use a database-level upsert with ON CONFLICT DO NOTHING.
Contingency: If duplicate notifications are reported in production, add a rate-limiting guard in the edge function that aborts if a notification for the same mentor and threshold was created within the last 20 hours, and add an alerting rule to Supabase logs for duplicate dispatch attempts.
The mentor visibility suppressor relies on the daily edge function to detect expiry and update suppression_status. A mentor whose certificate expires at midnight may remain visible for up to 24 hours if the cron runs at a fixed time, violating HLF's requirement that expired mentors disappear promptly.
Mitigation & Contingency
Mitigation: Schedule the edge function to run at 00:05 UTC to minimise lag after midnight transitions. Additionally, the RLS policy can include a direct date comparison (certification_expiry_date < now()) as a secondary predicate that does not rely on suppression_status, providing real-time enforcement at the database level.
Contingency: If the cron lag is unacceptable after launch, implement a Supabase database trigger on the certifications table that fires on UPDATE of expiry_date and calls the suppressor immediately, reducing lag to near-zero for renewal and expiry events.
The orchestrator needs to resolve the coordinator assigned to a specific peer mentor to dispatch coordinator-side notifications. If the assignment relationship is not normalised or is missing for some mentors, coordinator notifications will silently fail.
Mitigation & Contingency
Mitigation: Query the coordinator assignment from the existing assignments or user_roles table before dispatch. Log a structured warning (missing_coordinator_assignment: mentor_id) when no coordinator is found. Add a data quality check in the edge function that reports mentors without coordinators.
Contingency: If coordinator assignments are missing at scale, fall back to notifying the chapter-level admin role for the mentor's chapter, and surface a data quality report to the admin dashboard showing mentors without assigned coordinators.
The course enrollment prompt service generates deep-link URLs targeting the course administration feature. If the course administration feature changes its deep-link schema or the Dynamics portal URL structure changes, enrollment prompts will navigate to broken destinations.
Mitigation & Contingency
Mitigation: Define the deep-link contract between the certificate expiry feature and the course administration feature as a shared constant in a cross-feature navigation config. Version the deep-link schema and validate the generated URL format in unit tests.
Contingency: If the deep-link breaks in production, the course enrollment prompt service should gracefully fall back to opening the course administration feature root screen with a query parameter indicating the notification context, allowing the user to manually locate the correct course.