Provider Monitoring · Contents
Provider Monitoring
Monitored providersProvider changes & changelogRuntime Intelligence overviewAPI errors & failuresProvider incidentsRate limit eventsCode break detectionDeprecated APIsAuto-fix PRsImpact EngineAPI Fire DrillDeploy day checklistAlertsNotification preferencesEmail alerts & delivery statusAgency ModeClient invites & email statusDeveloper CLISlack integrationSettings overviewTheme (light / dark / system)API keysSecurity model & privacyPrivacy PolicyTerms of ServicePlans & billingTroubleshootingFAQProvider Monitoring
Troubleshooting
Common issues and their fixes.
- 'Email failed — sender not configured': the backend RESEND_FROM_EMAIL is unset. Configure a verified sender (see environment configuration).
- 'No data yet': the provider hasn't produced collected runtime data yet — this is honest 'not available', not a bug.
- Scanner finds nothing: confirm the repository contains monitored providers, or trigger an on-demand scan.
- Alerts stopped: check notification preferences, the daily caps, and that your GitHub connection is still active.
- Can't sign in: make sure your GitHub email is verified.
Related articles