Why messages enter a queue
When a campaign starts, OwlReach does not open one connection and fire every message at once. It reserves eligible recipients and dispatches individual jobs so each message can be tracked, retried, and recorded independently.
Limits and spacing
- The SMTP profile daily limit caps messages reserved through that server.
- The campaign send limit caps one campaign; zero means use the SMTP capacity.
- Jobs receive randomized delays rather than leaving in a single burst.
- Suppression and email verification checks happen before delivery.
Retries and failures
Transient transport errors can be retried by the queue job. Each attempt is recorded in Mail log. When retries are exhausted, the recipient becomes failed with the provider response, and you can correct the issue and use the one-click Retry action.
Production requirement
A database queue alone does not process itself. Production needs a queue worker and scheduler, or the combined owlreach:cron command configured by your deployment operator. If the worker is stopped, records may remain queued or show a stale sending state until the system reclaims them.
TARGET LOCKED