One of our analysts is having an issue where a job is not being started when it should due to the default date of a date variable prompt set object falling out of range of of the specified calendar.
Calendar keyword definitions seem to be on a rolling 4 year period, rather than just applying to all dates before and after the current date.
When running the job automatically from a schedule it's currently pulling the default date from the prompt set object as designed. This object allows you to input a date when you run it manually but it has to have a default value (currently 2015-12-31) when called from a schedule and can't be set to nothing.
The issue is the default date has to fall in to the range specified in the calendar definition for LAST_DAY_MONTH in CALENDAR to be considered valid. This range appears to be shifting so it only covers 4 years at a time.
It is currently valid between January 2016 and December 2019. 2015-12-31 seems to have dropped off the valid range last month so the job is not triggered when it should be.
I've attempted to use the NOW_MINUS UC_CLIENT SETTING but that isn't allowing date selection of past dates.
Any thoughts are appreciated.