Dollar Universe jobs or tasks fail to launch or schedule when the execution date falls outside the pre-defined calendar coverage. This typically results in errors in the universe.log or within the Univiewer Console (UVC) task simulation.
begin date [yyyy/mm/dd hh:mm:ss] after end date [yyyy/mm/dd 23:59:59]. Calendar's limit may be overtakenuniverse.log contains errors such as:
ERROR|X|IO |pid=...| buildDay | [TASK_NAME][MU_NAME] - year is outside the bounds of calendar [2018-2025]: 2026. Force it to calendar periodThe job is scheduled to run on a date that exceeds the current calendar end-date. This can be seen in the menu Design - Environment - Calendars, look for the End Year.
Expand the calendar coverage using UVC or the command line (uxadd cal) to add at least the current year + 2 as indicated in the documentation.
Check current calendar coverage.
%UXEXE%\uxshw cal exp mu="MU_NAME"$UXEXE/uxshw cal exp mu="MU_NAME"Add future years to the calendar.
%UXEXE%\uxadd cal exp mu="MU_NAME" since=2026 before=2035$UXEXE/uxadd cal exp mu="MU_NAME" since=2026 before=2035Verify the expansion by running a task simulation for a date in the newly added range.
%UXEXE%\uxlst prv upr=upr_name ses=ses_name mu=MU_NAME dsince=01/01/2026 dbefore=01/02/2026We recommend to have a reference calendar for all the nodes and areas and distribute this calendar globally in case of any changes like the Holiday days.
For further guidance on CLI syntax, refer to the . If the procedure is unsuccessful, contact .