Finding Start Time Exceeded Tasks after outage
Article ID: 404301
Updated On:
Products
Issue/Introduction
When an outage occurs or clients are stopped, there are some tasks that get skipped within schedules. These tasks get a status of ENDED_TIMEOUT - Start Time Exceeded, but they cannot be searched for using the {client_id}/executions rest endpoint or using Process Monitoring or Executions. Is this expected behavior? Is there a way to find these?
Resolution
This behavior is by design - the tasks never had an AH id number (RunID) because they never were activated or started. There is a way to find these through a SQL Statement:
If the schedule is still active:
select * from ejpp where ejpp_status = 1941
1941 is the status for ENDED_TIMEOUT - Start time exceeded.
ejpp_ah_idnr is going to be the schedule runid. epp_starttime and ejpp_endtime are when the schedule was activated. ejpp_object is going to be the object name within the schedule.
ajpp has the same info, but is for completed schedules (not active) - it can be used like:
select * from ajpp where ajpp_status=1941
Additional Information
Feedback
