If you noticed chats have been launched outside of chat hours set in the .NET Console, it is very likely that you are using a custom implementation which sets the chat queue ID in the chatAuthenticate API call, bypassing Chat Business Rules. 

 

When adding the QueueId in the chatAuthenticate / establishSessions API call, the Chat Hours check is skipped in the requestEngagement API call. This is working as designed and can be beneficial especially for chat bot implementations. 

 

If your business requirements are to set the chat queue ID in the requestEngagement call, but you don't want chats to enter the queue when there are no agents logged into Chat, you can achieve this by enabling configuration setting USER_DISCONNECT_IF_NO_AGENTS. More details on this matter can be found in Answer ID 7887: End user chat is not displaying "AGENTS_AVAILABLE_CHAT_PLEASE_TRY_MSG" message. 

 

See also Answer ID 2166: Changing the support hours on the Chat page