Event with multiple schedule criteria fails to trigger on the last day of the month

Products

• ESP dSeries Workload Automation
• ESP dSeries Workload Automation - Scheduler (dSeries)

Issue/Introduction

An Event is configured with multiple schedule criteria to ensure it runs every weekday and also on the last day of the month (regardless of whether that day is a weekend). However, the Event fails to trigger when the last day of the month falls on a Saturday or Sunday, despite the "Test" function showing the schedule is valid.

Event Schedule Criteria:

Schedule: 8:00 PM weekdays

Schedule: 8:00 PM last day of month except weekdays

Symptom: On Saturday, February 28th, the Event did not trigger, even though it was the last day of the month and not a weekday.

Environment

ESP dSeries Workload Automation (DE)

Cause

Due to multiple schedule statements defined within the Event, conflicts can arise from the schedules between "weekdays" and "Except weekdays" logic.

Resolution

To avoid conflicts within the scheduler, the best practice is to separate the criteria into two distinct Events that trigger the same Application.

For example:

Step 1: Create/Modify Event 1 (Weekday Run)

• Event Name: SCHED.ETL_WEEKDAYS

• Schedule: 8:00 PM weekdays

Step 2: Create/Modify Event 2 (Month-End Weekend Run)

• Event Name: SCHED.ETL_MONTHEND

• Schedule: 8:00 PM last day of month except weekdays

Result: By using two separate Events, the scheduler evaluates each rule independently. This eliminates "Except" logic conflicts and ensures that if the last day of the month falls on a Saturday or Sunday, Event 2 will trigger successfully without being influenced by the weekday-only rule of the other criteria.

Note: Use List Scheduled Events to test the Event.