I have this same issue on one instance and not others. Not great when holidays do not work as expected.
20.0.7.1080. Looking back at updates, this seems to have begun after the overlapping "year" feature was updated in the holiday scheduler. Something has broken the call flows for holidays.
Forward dates do not activate holidays. Current dates do not activate holidays. Partial or complete days do not make a difference. I can manually activate them.
After meticulously going through all departments, Office hours, users, trunks, DID's, queues etc etc I cannot resolve the issue.
All departments are matched end-to-end for the routed calls. I attempted with holidays.cs script enabled and disabled. Holiday prompts added or removed. User forwarding checked, status checked, and I've reached my level of willingness to dig.
The call flow logging shows holiday mode is detected as active but is not actioned. It detects holidays, then routes to OOH or even worse, delivers the call. Out of office, call forwarded
12/29/2025 5:55:11.252 PM [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:***
12/29/2025 5:55:11.252 PM [Flow] It is holiday today
12/29/2025 5:55:11.252 PM [Flow] Looking for inbound target: called=**********; caller="**********" <sip:**********@:0>
If I manually override the office hours and put any of the affected departments into holiday mode, they process the routes as expected. On holiday, call forwarded
My client installation with the holiday routing issue is 20.0.7.1080. This particular installation is a backup restored from a failed V18-V20 upgrade.
I have no choice now but to manually update this instance for all holidays, other than to route to an IVR using break times - if they work.
Also, poor response from you above ivank, Adrian was asking for help, not asking to be dismissed.