Campaign actions not being sent

If your campaign seems stuck, work through these causes in order. Together they cover nearly every case.

1. Account disconnected. Check the dashboard or run 'get_account'. A disconnected sender cannot send anything; reconnect and the queue resumes on its own.
2. Daily limits reached. 'get_account' shows per-category daily_limits with used, limit, and remaining. When remaining hits 0 for invitations or messages, sending resumes after the reset at midnight UTC.
3. Outside the send window. Each sender account has a business-hours window in its own timezone. 'get_account' returns send_window with in_window and next_open_at, so you can see exactly when sending resumes. Adjust it with 'manage_outreach_settings' action 'business_hours'.
4. Campaign paused or never launched. Outreach must be enabled: launch it (in the CLI: crispy campaign launch <id>), or resume it with 'manage_outreach' action 'resume'.
5. Nothing left to send. Contacts already connected to the sender, invited recently (LinkedIn enforces a resend cooldown of roughly three weeks), on the block list, or permanently unreachable are all skipped by design.

The quickest diagnosis is the campaign state snapshot: crispy campaign state <id> in the CLI, or 'get_campaign' with include 'state'. It returns the funnel plus stall info with a reason.

Also remember that sending is deliberately spread out. The daily budget drips across the day in randomized slices rather than firing all at once, so a quiet hour is normal and not a stall.