Send windows, daily limits, and pacing

Campaign send windows & daily limits

Each campaign configures:

• send_windows: timezone + weekday hourly slots during which outbound is allowed for invite/dm pacing.
• daily_limit: throughput guard for outbound invites respecting provider safety.
• Optional minimum / maximum spacing jitter between attempts (helps avoid deterministic bot-like cadence flagged by automation detectors).

Fulreach converts these into timestamps written on queued prospects and auto-DM queue rows; background runners pick due work only inside allowed windows.

Sequence-specific behaviour

Automated multi-step sequences use a separate architecture (database-authoritative schedule + reliable job queue) with catch-up days options for follow-ups (for example extra weekdays like Saturday for sequence-only paths without broadening non-sequence invite windows). Sequences re-check windows at send time—if you move windows after scheduling, some jobs may reschedule rather than fire immediately.

Duplicate invite guard (24h)

Before each connection invite send Fulreach checks recent send_log entries for the same LinkedIn account + prospect ID with statuses like sent, pending_confirm, rate_limited inside 24 hours—blocking accidental double invites that risk provider penalties or duplicate provider graph edges.

Transient transport-class failures don’t block legitimate retries the same way.

Provider rate limits & pausing

When LinkedIn/Unipile signals invitation capacity exhaustion (often surfaced as 422 / cannot_resend_yet patterns), Fulreach classifies whether it is per-prospect vs account weekly/daily limit and may set resume-after timestamps on campaigns so automated sends respect the next safe local window.

If sends pause unexpectedly look for Needs attention style classification in UI or support-readouts—often resolved by waiting for window reset or lowering daily aggressiveness.

Practical tips

• Warm new senders with conservative daily limits before scaling.
• Align send windows to human business hours in the prospect timezone when possible.
• Don’t stack multiple hyper-aggressive campaigns on one LinkedIn identity without monitoring limit reached states.