Global Holiday "every year" setting not being honored

[ebrowne_sts]

We set holiday schedule on one of our client's 3CX for Dec 24 and Jan 2nd, every year. Here comes today and it's still routing to their Normal IVR and not the HOL one. Had to change from every year to Jan 2nd 2023 specifically for it to work.

I saw a previous post about this back in 2017 and though it was fixed:
https://www.3cx.com/community/threads/holiday-days-from-last-year-didnt-run-this-year-nye.53244/


Also, when posting this, the "System" required field is not showing the actual affected system even though its licensed and in our partner portal, so I had to select our main 3CX in order to post.

 

[SB2021]

We had the same issue with the "every year" setting not working, when we changed to the specific year (2022) it worked. Can we clarify if this is a known issue?

Also checking the systems we set a specific year on they have now reverted to "every year", can we clarify this is because the year changed?

 

[SteveITS]

Also checking the systems we set a specific year on they have now reverted to "every year"

Interesting catch, I see this as well. 12/26 does not show every year:

but if I open it, without making any changes, it does show there:

(the other two "observed" days do show a year because I had already opened them and corrected them to 2023 to see what would happen)

We had an issue I think a couple years ago where a holiday did not process as a holiday and I'm pretty sure it was Jan. 1.

 

[SteveITS]

Ah, this is because the holiday dates were set to 2022, and 2022 is no longer a choice in the dropdown. So 3CX is presumably defaulting to "every year" as the first choice. That is confusing. I wonder if it would process on that day in 2023, or ignore it?

 

[ebrowne_sts]

Ah, this is because the holiday dates were set to 2022, and 2022 is no longer a choice in the dropdown. So 3CX is presumably defaulting to "every year" as the first choice. That is confusing. I wonder if it would process on that day in 2023, or ignore it?

In our case it was set to "every year" for Jan 2nd but ignored it this year and routed calls normally. I had to explicitly say 2023 for it to work.

 

[SteveITS]

In our case it was set to "every year" for Jan 2nd but ignored it this year and routed calls normally. I had to explicitly say 2023 for it to work.

Yeah, I was replying to myself, I guess that wasn't clear the way I worded it, since one can't reply that way through the forum. Two different issues.

I did not try Jan. 2. I do occasionally try holidays since it didn't work that one time, before. I am pretty sure I tried Christmas, or the day after.

 

[SB2021]

OK done some further testing and i believe this is happening.

As we have seen when you set the year and then the year ticks over it switches to "every year", but i believe it retains the year setting so when you look at it next year you leave the "every year" setting and adjust the date only to suit and it does not work. So make sure you adjust "every year", it also works if you adjust the setting to a year and change it back again to "every year", this may actually now work every year.

 

[GOKALLIT]

Today is MLK day and our client last week gave us a list of all the holidays to enter in the phone system. Very embarrassed because the global holiday function did not work. After troubleshooting, I changed the "EVERY YEAR" to 2023 and it worked as should. Not sure why "EVERY YEAR" did not function.

 

[SteveITS]

the global holiday function did not work. After troubleshooting, I changed the "EVERY YEAR" to 2023 and it worked as should. Not sure why "EVERY YEAR" did not function.

Per the above posts, and because MLK day changes each year, it was probably set to "2022" but since "2022" is not a choice in the dropdown when the entry is edited, the editing screen shows it as the first choice in the dropdown "every year" which is incorrect. IOW it's a display bug.

Take a look at the picture I posted above. Before your edit, did that screen have text in the "is every year" column, where I highlighted in yellow? If it had been set to 2022 that column would have been blank.

 

[ltri37]

This is a pretty important malfunction. Has anybody filed a formal support ticket for this?

 

[SteveITS]

In terms of functionality, setting a holiday for Jan 15 2022 shouldn't have it trigger for 2023, regardless of what the display shows. I agree having it show the wrong thing is very confusing.

ebrowne_sts was describing a different issue though, where it wasn't triggering at all even if set to Every Year. Just want to be clear on that. I didn't see that this year but have in the past, a year or two ago.

I suppose a separate question is, what happens if someone opens the Jan. 15 2022 entry, which incorrectly shows as "every year," changes only the date to Jan. 16 and saves it. Does it save as Every Year, or remain 2022? (it should show either "Every Year" or blank in the "Is Every Year" column in the table) All our clients are updated for 2023 so I don't have any 2022 dates to test that.

No I haven't opened a ticket. We're not quite Bronze yet so don't get any free cases. :-/

 

[SteveITS]

I did eventually open a case for the not-displayed year per a discussion in thread https://www.3cx.com/community/threads/troubleshooting.120557/. TL,DR: the lack of year display is not a bug. Just don't save it with Every Year selected.

 

[Lee Cramman]

it might not strictly be a 'bug' as 3CX see it, but it is behaviour that's as confusing as hell and has led to errors affecting multiple customers.

I would suggest that the validation (i.e. allowing you to set dates in the past) and display handling need further work.