Execution date is moved forward when a non-existent day is specified in the Job Scheduler

User Experience
, , , ,
1

Hi,

I am having trouble setting up the job scheduler.

◆Record
Dev Studio
　SysAdmin⇒Job Scheduler

◆Settings
Schedule：Monthly
Select：Day 31 of every 1 month(s)

If the above settings are used, there is no problem for months that exist up to 31 days (e.g., January and March).

However, for months that only exist up to 30 days (e.g. April and June), Job Scheduler that was created with the assumption that it will start on the 31st will be scheduled to start on the 30th.

If the 31st does not exist, I would like to prevent the Job Scheduler from starting in that month.

Is there a better way to do this?

2

@YutaI205 I can think of an approach-> as we already know for which months job scheduler processing should not happen, we can keep this stopping logic in the job scheduler activity. In the first step you can use a when conditions, which uses decision table to check if it’s expected month, if no you can do exit activity.

3

@Anoop Krishna I understand that this problem is not something that can be worked around in the Job Scheduler settings.
I will modify the activity to check the date on the activity side as you have indicated.

Thank you very much for the very useful information.