Enginy runs campaign steps through two execution queues. This is what drives “Pending” items, pacing, and why some campaigns take longer to progress than others.
Queue overview (Email vs LinkedIn)
Email queue: only includes Send email actions.
LinkedIn queue: includes actions that hit LinkedIn and can be rate-limited, which may create status Pending actions and slow down execution across campaigns using the same identity.
LinkedIn actions that can be rate-limited
These actions can enter the LinkedIn queue and wait their turn:
LinkedIn action | Rate limit | Daily cap | Notes |
Visit profile | 1 visit every 4 min | 50/day (150/day with Premium) | Can generate Pending if the queue is busy. |
Like last post | 1 like every 5 min | No daily max | Still rate-limited by time. |
Send connection request | Configured by the user | Configured by the user | Controlled in Identity settings. |
Evaluate connection request | 5 evaluations every 30 min | No daily max | Throttled in batches. |
Send message | Configured by the user | Configured by the user | Controlled in Identity settings. |
What runs instantly (non-LinkedIn nor email actions)
Everything else is near-instant (or completes very quickly depending on server load). These are typically “Enginy-side” operations, like:
Evaluating conditions (e.g., has LinkedIn URL, is a connection, etc.)
Branching logic and internal checks
These steps may technically pass through the same pipeline, but they clear fast and priority barely impacts them.
How delays affect pacing
Campaign steps are also governed by time delays between actions.
Important nuance: when a queued LinkedIn action finally executes, Enginy doesn’t automatically run the next step immediately unless the delay before that next step has already elapsed. If the delay is still running, the lead waits until the delay finishes — then the next eligible action can be queued/executed.
How Enginy prioritizes queued LinkedIn actions
When multiple LinkedIn actions are waiting in the queue, Enginy prioritizes them using this order:
Lead message depth first
If two queued items are both Send LinkedIn message, Enginy sends first to the lead who has already received more LinkedIn messages earlier in the sequence.Campaign priority second
If the leads have the same number of prior messages, Enginy uses the campaign’s Priority (High > Medium > Low) to decide what goes first.Random tie-breaker
If both message depth and campaign priority are identical, execution order is random.
This model keeps long-running conversations moving forward while still letting you “fast-track” higher-priority campaigns when there’s a tie.