If your LinkedIn outreach campaign is not sending, first check whether the ZenMode desktop app is open and online. ZenMode’s getting-started guide says the Mac or Windows app needs to be open to send connection requests and follow-ups. If it is, do not assume the campaign is broken—or that leaving the app open will fix it. Check whether the campaign can run now, then whether any contact has an action due.
First, rule out an interrupted run
Check your internet connection, open the desktop app, and look at the sending account’s LinkedIn connection. The getting-started guide says a working LinkedIn session shows a green Connected status. If it does not, resolve the connection before interpreting an empty activity count as a prospect-list problem.
Next, check whether the campaign is active rather than paused or completed. A newly created campaign auto-starts when the desktop app is open, according to ZenMode’s setup guide; that does not mean reopening the app starts every idle campaign. For an API-queued lead, ZenMode’s API documentation explicitly says someone must click Run on the desktop: opening the app alone is insufficient. Treat that Run instruction as specific to the documented queued-lead workflow, not as a required fix for every campaign.
Then, check when sending is allowed
Compare the current day and time with the campaign’s configured business hours. ZenMode says actions run during those hours and uses randomized delays between actions, so a quiet interval—even with the app connected—is not proof of a failed send. Check the configured window before changing targeting or restarting anything.
Fictional example: a campaign sent invitations yesterday but shows none this morning. The app is open, the LinkedIn session is connected, and the campaign is active. Its configured business hours begin later today. The next action is to check activity during that window, not to replace the prospect list. If the window passes without activity, continue to the contact-level check rather than concluding that the schedule was the only cause.
Separate a stopped run from nothing due to send
Open the campaign detail page to inspect individual contact statuses, then compare them with the desktop app’s Today’s Activity panel. ZenMode’s guide identifies the detail page as the place to see each contact’s status and the panel as a view of requests, acceptances, replies and meetings. A flat Requests count tells you what happened today; contact statuses help you investigate what could happen next.
- If there are pending prospects who appear ready for an invitation, but the app is connected, the campaign is active and business hours are underway, check for a pause or an applicable sending cap before treating the list as empty. ZenMode says it enforces account-level daily and weekly pacing caps and allows a lower daily limit on each campaign. Do not raise a limit merely to force activity.
- If you expected follow-ups, look for accepted connections whose next scheduled follow-up is due. ZenMode says follow-ups are spaced a few days apart after acceptance and stop when someone replies. A pending invitation, a follow-up scheduled for another day, or a replied-to conversation is not an overdue follow-up.
- If invitations were being refused, check whether the account’s campaigns are in ZenMode’s documented weekly pause. The setup guide says this pause resumes automatically the following Monday. Do not try to get around that pause to produce a send today.
Decide whether to wait, investigate or ask for help
The decision is whether an action is actually expected now. If the app was closed or the connection was lost, restore that prerequisite and observe the campaign during its permitted hours. If the campaign is manually paused, review it and resume it when appropriate; if it is completed, do not expect it to resume on its own. A documented weekly pause resumes automatically the following Monday. If the campaign is outside business hours, at a limit, or waiting for an acceptance or follow-up date, wait for that condition to change. If a particular contact appears due during business hours and no action follows while the app and campaign remain available, gather a precise report instead of repeatedly changing settings.
For API-queued leads specifically, ZenMode’s API documentation also describes conditions such as account cooldown, a reached per-account daily limit and a lead awaiting warm-up. Its delivery assessment reflects what the server could see when the lead was pushed, not a promise that it will send. Do not use an API response or its pickup estimates as a universal diagnostic for campaigns created in the dashboard.
If the campaign remains idle when an action appears due, record the campaign name, sending account, expected action, affected contact and visible contact status. Add the local date, time and time zone; configured business hours; whether the app was open and online; LinkedIn connection and campaign state; the last observed send; and any relevant activity counts or notice. That gives support a specific expected-versus-observed case to investigate. ZenMode’s getting-started guide lists hello@zen-mode.io for help. If LinkedIn has issued an automated-activity restriction notice, follow the notice and read What Actually Happens When LinkedIn Restricts Your Account rather than trying to restart sending around it.
