Post Upgrade 15.9.1: Scheduled Job System Error
search cancel

Post Upgrade 15.9.1: Scheduled Job System Error

book

Article ID: 211333

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

After the 15.9.1 upgrade, some scheduled jobs cannot be displayed. When opened the scheduled jobs, the following error message will be displayed and the scheduled information is not shown.

"ERROR System error. Contact system administrator."

app-ca.log shows the following error message.

ERROR 2021-03-24 16:27:26,281 [http-nio-8080-exec-16] niku.xql2 (clarity:admin:6046238__92C64D16-A3A7-4A36-A9B1-FCEB222C4A7D:nmc.jobProperties) 
Internal Processing exception
java.lang.Exception: Failure while evaluating "toDaysOfWeek(@START_DATE,@DAYS_OF_WEEK)"
in expression "{toDaysOfWeek(@START_DATE,@DAYS_OF_WEEK)}" error: Invalid expression toDaysOfWeek(@START_DATE,@DAYS_OF_WEEK):
For input string: "1-5"

Steps to Reproduce: 

  1. Go to 'HOME' > 'Reports and Jobs' and open 'Jobs' tab. 
  2. Open a certain job and click the 'Set Recurrence' link.
  3. Click the radio button next to 'Use Unix Crontab entry format' and specify the schedule that contains "-" in the fifth attribute. E.g. " "0 2 * * 1-5".
  4. Specify required fields and click 'Submit' button.
  5. Open the created scheduled job.
    ---> 
    The error message "ERROR System error. Contact system administrator." is displayed and the specified schedule is not displayed. 

Expected Results: 
The scheduled job is displayed with the specified schedule settings.

Actual Results:
All settings are not displayed with the error message.

Environment

Release : 15.9.1

Resolution

This is reported as DE60181 and is working as designed.

Clarity does not support the full UNIX crontab syntax, just a selective set.

Clarity does not support "-" or "/" as Cron operators.
Clarity supports "," as a separator for days of week.

If creating a new job instance with the invalid crontab entry, the error will appear.

If updating an existing job instance, the job instance can be updated, therefore the workaround is to change the definition from the "-" notation to the comma-listed notation. 

Example, if the crontab entry is:
0 2 * * 1-5

The change required is:
0 2 * * 1,2,3,4,5