# Seeking Help With Configuring One-Way Connectivity **URL:** \ **Category:** Service Monitoring\ **Tags:** notifications, icinga-for-windows, director, icinga2\ **Created:** [November 21, 2025, 7:54pm UTC](https://community.icinga.com/t/seeking-help-with-configuring-one-way-connectivity/15269 "2025-11-21T19:54:48Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![XilityWorks](https://community.icinga.com/letter_avatar_proxy/v4/letter/x/7ba0ec/32.png) [@XilityWorks](https://community.icinga.com/u/XilityWorks)\ **Post date:** [November 24, 2025, 7:48pm UTC](https://community.icinga.com/t/seeking-help-with-configuring-one-way-connectivity/15269/6 "2025-11-24T19:48:04Z")
These are notifications (emails or other). Do you mean check interval? All devices are checked 24/7. I don’t have a great way to change that. If you meant interval, the parent service is set to 3 soft states while the offending are 6. This adds 3 minutes of buffer. I’m somewhat confident it isn’t a notification delay issue. 5 soft states would still take 5 minutes to come online, get connected, and perform a successful check. This morning, I can see this timeline: ![image](https://community.icinga.com/uploads/default/original/2X/0/0bd8dbaab82e441ce5991fb8b265c6717f2f955c.png) To me, this looks like the first of 5 soft states were reached on Sunday. We sent a single admin notification. This would be after-hours work so it doesn’t send to primary/secondary. But then when the device comes online at 8:10:46, it notifies everyone via Teams then primary and secondary that there is an issue… before immediately sending an “ok” 1 second later. This exact behavior occurs for every service. --- _[View the full topic](https://community.icinga.com/t/seeking-help-with-configuring-one-way-connectivity/15269)._