Configure test email alerts
Send failure and recovery notifications for decisive integration-test transitions while retaining a durable delivery record.
Enable delivery
Configure Cloudflare Email Service and verify the organization's sender domain. On the API Worker, set:
| Setting | Value |
|---|---|
EMAIL | The send-email binding. |
TEST_ALERT_FROM | An address on the verified sender domain. |
TEST_ALERT_TO | The destination for failure and recovery alerts. |
Restrict the binding to the intended recipient. When changing the destination, update both its restriction and TEST_ALERT_TO. Apply the release's database migrations before enabling delivery.
Use addresses owned by your organization. The sender domain, account eligibility and recipient restrictions need live verification. Omitting both sender and recipient disables test email; partial configuration is rejected.
Test the behavior
Run a failing check, correct the condition and run it again. The first observed fail or error sends a failure alert; a later pass sends recovery. Repeated failing results do not send repeated alerts. Skipped and needs-review results do not change the decisive health state.
Email configuration does not enable the check scheduler. Confirm which cron or manual runs actually execute in your installation.
Investigate delivery
Provider acceptance does not establish inbox delivery. Check the email activity log and Sparta's delivery records.
An uncertain send remains claimed to avoid duplicate messages. Reconcile it against the provider before retrying; do not clear a claim merely because it is old.
See troubleshooting for run and permission failures.
Plan a release update
Review a release, preserve recoverable state and validate a staged upgrade before changing an installed compliance workspace.
Connect an MCP client
Understand the authenticated MCP endpoint, role limits and the difference between managed-account and Cloudflare Access client authentication.