Actions seem slow or delayed

Crispy intentionally spreads actions out to protect your account. If sends look slow, that is the system working as designed.

How pacing works

• A campaign's daily budget is never fired at once. Each processing tick sends only a slice of what remains, sized so the budget spreads across the whole day, with randomization so the pattern never looks mechanical.
• Individual sends inside a tick are separated by short randomized delays.
• Business-hours windows gate sending to the sender's local working hours. Outside the window, actions wait until it reopens; 'get_account' shows send_window with next_open_at.
• Follow-up sequence steps fire at their configured delay after a connection accepts, not immediately.

A real person does not fire a whole day's outreach in two minutes, and bursts like that are the classic trigger for LinkedIn restrictions. The drip is deliberate.

What's normal

• A campaign sending a few invitations every couple of hours during business hours: normal.
• Nothing at all for a full day: not normal. See 'Campaign actions not being sent' for the checklist (disconnected account, exhausted limits, paused campaign, out-of-window, or an exhausted list).

If you want to know when the next send can happen, 'get_account' gives you both the per-category remaining budget (which resets at midnight UTC) and the next send-window opening time.