Skip to main content
All CollectionsOutreach Campaigns
Why my LinkedIn sender is Out of Working Hours?
Why my LinkedIn sender is Out of Working Hours?
Updated this week

What our users are most confused about is when they see an ongoing (active) campaign, but for the LinkedIn sender(s) they see a message displayed with red letters > Out of Working Hours!

Well, the LinkedIn senders have their own time zone, weekly schedule, and working hours set when being included in a specific campaign.

🚨 The LinkedIn sender can have different working hours for different campaigns.


The Out of Working Hours feature basically states that the LinkedIn sender(s) is offline until the working hours schedule set hits its time and day.

Regardless of whether the campaign is ongoing, the LinkedIn senders will not execute any actions until the working hours that are previously set start.

Also, the Out of Working Hours feature can be the answer to requests like asking why the LinkedIn sender did not execute any actions for a specific day. The best way to check and eliminate this matter is to click on the clock icon next to the LinkedIn account's name.
​

By clicking here, the working hours' screen will pop up on the right side of the campaign screen, and there you can view which time zone, and especially which days and what time of the day the LinkedIn sender was set to work and execute actions.

In order to learn how to adjust the working hours and get rid of the Out of Working Hours state, click on this article that will show the steps on how to reconfigure the working hours.

Also, the second confusion that usually users have is when they see the same LinkedIn sender in two different ongoing campaigns, and in one the same sender is active and in the other is Out of Working Hours.

Again, this is due to the possibility of having a specific working hours schedule for the same LinkedIn sender in each campaign connected. But as you already know, you can quickly resolve this by adjusting the working hours and setting the LinkedIn sender active again.

Did this answer your question?