Queued vs. sent
The distinction dashboards blur: queued means the system plans to send; sent means it actually left. Reporting queued as sent is how tools fake momentum.
A queue contains intended work; execution records describe what happened afterward. Check campaign schedules for blocked or waiting work and volume reports for recorded sends. When a send outcome is uncertain, inspect the timeline before retrying or reporting a definitive failure.
In practice
Read the campaign schedule for queued work, then compare recorded outbound events for the same seat and period.
What to check
Queued, ready, dispatched, confirmed, and replied are different states. Do not report a timeout as a failure to send without checking the recorded outcome.
Use it in LinkedBoost
- get_sequence
Inspect campaign copy, performance, and the work waiting to send.
- get_outreach_volume
Count recorded outbound events over a time window.
- get_activity_event
Inspect the recorded payload and outcome of one operation call.
Related terms
- Envelope response
- A consistent structured reply shape from every tool call: success flag, data, a one-line summary, notable signals, and durable learnings: so an agent always knows what happened and what deserves attention.
- Follow-up sequence
- The planned messages after the first touch: classically an invite, an acceptance-gated opener, then two or three spaced follow-ups over 10–14 days.