Event Fails to Trigger if Schedule is Older than 2,169 Days
search cancel

Event Fails to Trigger if Schedule is Older than 2,169 Days

book

Article ID: 138364

calendar_today

Updated On:

Products

CA Workload Automation DE - Business Agents (dSeries) CA Workload Automation DE DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries) CA Workload Automation DE - Scheduler (dSeries)

Issue/Introduction

We ran into a situation where one of our production events did not trigger. Upon looking at the schedule statement it was "Every 14 days starting 2013/04/22 06:00" I did some testing and found that the product doesn't seems to like any dates that are older than 2,169 days. More tests concluded that I was able to save an event with  a schedule statement of "Every 14 days starting 2013/09/28 06:00" but I cannot save the event with a statement of "Every 14 days starting 2013/09/27 06:00" (one day less) and I receive the error below. This is a concern of ours because we have to be careful with putting starting dates and will have to eventually update them so that the event continues to trigger. Could this please be addressed?

Failed to schedule the event SCHEDMASTER.CAWA_VERIFY: Could not resolve the next scheduled execution for event SCHEDMASTER.CAWA_VERIFY. Check your schedule criteria.
Could not resolve the next scheduled execution for event SCHEDMASTER.CAWA_VERIFY. Check your schedule criteria.

Environment

Release : 12.x

Component : CA WORKLOAD AUTOMATION DE (DSERIES)

Cause

The DE Server evaluates the schedule criteria and calculates the next execution of the Event for the future from the starting date/time, in this case 2013/04/22 06:00.

However, there is a limitation on the number of times the DE Server can evaluate the schedule criteria to get the next execution time.

See Could Not Resolve the Next Scheduled Execution for Events

Resolution

The suggestion is update the Event schedule criteria with no date or date not too far off.