Why a send is deferred, not skipped
Last verified 2026-07-28
This guide describes deferral states that apply after the required Connection and delivery setup are approved.
Once sending is available, an action that cannot run safely waits without losing the prospect's place. A safe wait may continue later. An unknown result from the connected service pauses until Klosent confirms what happened instead of risking a duplicate.
The reasons you'll see
- Outside working hours: waiting for the connection's window to open.
- Account at cap: the daily or weekly ceiling is reached.
- No account available: the Campaign has no connection for that channel.
- Connected-service limit: it waits until that service allows another attempt and stops automatically after the allowed retry limit.
- Unknown send result: it pauses while the result is checked instead of risking a duplicate. A confirmed rejection by the connected service does not retry automatically.