If everything is configured and nothing is sending, walk this checklist top to bottom. Each stage of the pipeline quietly does nothing when a prerequisite is missing, so the fix is almost always at the first check that fails.
Are opportunities coming in?
The sources page shows a last run time for every source. Ingestion runs daily at 06:00 UTC, so a source enabled five minutes ago has simply not run yet. If a source has run and your opportunities list is still empty, the source itself is failing; its last run error is shown on the same page.
Are they being scored?
An opportunity at status New has not been picked up by processing yet; processing runs every 30 minutes. After processing, the status is Scored for a Pursue or Partner verdict, or NoBid. Opportunities sitting at New for more than an hour mean the worker is not running or the workspace has no active sources.
Did enrichment find a contact?
Open the opportunity's detail page. If the contacts panel is empty on a Pursue or Partner opportunity, no enricher returned a contact; SAM.gov notices often list no point of contact at all. The workaround is to add the contact by hand from the enrichment queue.
Is there a sequence?
Auto-enrollment picks the first sequence whose agency type matches the opportunity, falling back to any sequence in the workspace. But it needs at least one to exist; an empty sequence list means every opportunity is skipped at enrollment.
Is the contact enrollable?
To be enrolled, a contact must:
- Have an email address
- Not be opted out
- Not be marked bounced
- Have a confidence score of at least 0.5
Contacts you add by hand default to confidence 1.0; auto-enriched contacts vary by source, and low-confidence ones will not enroll.
Is the daily cap hit?
Once the daily send cap in your outbound settings is reached, sending stops for the day and resumes at 00:00 UTC. A low cap is the right call in week one, and also the most common reason a healthy pipeline looks stalled by afternoon.
Is outbound email configured?
Without an outbound configuration, the sender does nothing at all. Verify outbound settings show enabled; even Console mode counts as configured, since the dry run exercises the full pipeline. The blocker is a missing configuration, not the choice of provider.
Is it inside the send window?
Each step has a UTC send window, 14:00 to 22:00 UTC by default. Outside the window, a due step is seen and skipped until the window opens. If you test at midnight Eastern, silence is the expected behavior.
Read the activity log
The most authoritative trace is the activity log in your workspace. Every stage emits an audit event:
OpportunityScoredDealCreatedEnrollmentCreatedEmailSent
Scored without EnrollmentCreated points at the sequence and contact checks above. EnrollmentCreated without EmailSent points at the cap, the configuration, or the send window.