Troubleshooting and Verifying Event Triggering in ESP dSeries

Products

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

Issue/Introduction

Users need to know how to verify if an Event has successfully triggered at its scheduled time or why it may have failed to trigger in ESP dSeries Workload Automation.

Symptoms

• An Event does not appear to have run at the expected time.
• The "Next Scheduled Time" for an Event is blank or shows a date in the past.
• Jobs within an application associated with an Event did not initiate.

Environment

 ESP dSeries Workload Automation

Cause

Common reasons for an Event failing to trigger include:

1. Schedule Criteria Limitation: The DE Server cannot evaluate schedule criteria where the start date is more than 2,169 days in the past.
2. Logic Conflicts: Multiple "Schedule" and "Except" statements within a single Event can cause calculation conflicts.
3. Time Zone Mismatch: In High Availability (HA) environments, mismatched time zone labels between servers can prevent triggers.

Resolution

To determine if an Event was triggered or if it missed its schedule, use the following methods:

1. Check the Next Scheduled Time:

   • In the Desktop Client or Web UI, open the Event definition.
   • If the Next Scheduled Time is in the future, the scheduler has successfully calculated the next run.
   • If it is blank or shows a past date, the Event likely has a scheduling conflict or an expired start date.

2. Use the Simulate Function:

   • Right-click the Event and select Simulate.
   • This utility generates a list of future execution times based on your current criteria and calendars, allowing you to verify if the scheduler "sees" the expected time.

3. List Scheduled Events:

   • Use the List Scheduled Events feature to see a forecast of upcoming triggers across the environment. If an Event is missing from this list, its criteria might not be met or it may be suspended.

4. Review the Server Tracelog:

   • Search the DE server tracelogs for the specific Event name.
   • The logs will indicate if an execution attempt was made, if it was "bypassed," or if a specific error occurred.

5. Verify Start Dates:

   • If the Event uses a specific start date (e.g., "starting January 1, 2018"), ensure this date is not more than 2,169 days old. If it is, update the criteria to a more recent date or remove the "starting" clause.