iDash triggering false SLA_MISSED_END alert when job has already completed

Products

• iDash Workload Automation

Issue/Introduction

We have job that runs from 8 pm-10 pm every night and that job has a SLA deadline on iDash for 5:30am. That job has been completing at 11:00pm at night successfully before the deadline but at 5:30am it will start triggering SLA_MISSED_END alerts on WCC.

Environment

Release : 12.0.4, 12.0.5

Cause

The problem is that the completed job statuses are hanging around in memory when idash wasn't able to process an exit workload event.

Resolution

As a workaround, you can restart iDash service to clear the memory. This issue have been fixed in the upcoming 12.1 release, which should be GA in August.