Closed incident reactivated !!
We faced a new issue of reactivated closed incident. The incident was resolved on 7th Feb and should be closed by 21st Feb, as we have applied closed setting for 14 days but the user reactivated the incident on 22nd and it got reactivated.
Kindly suggest.
Answers
Im guessing your using cireson autoclose MP to do this
could it be the case that the incident was reactivated on the 22nd before the workflow for autoclose run? as even though its set at 14 days this is only applied once per day when the autoclose workflow runs?
can you confirm that the incident actually went from resolved into the closed state in the history?
The Cireson Auto Close workflow runs at 5 am and the incident should get closed by 22nd Feb at 5 am.
The incident did not went to resolved state as I can see in the history.
The Cireson Auto Close workflow is running without any issues and we received this error for only a single incident.
When the incident was originally resolved
When the incident was moved from resolved to closed
when the incident went from closed to Active after it was re-activated
thanks
Dave
There is no history of getting incident into closed state.
The incident was activated on 22nd Feb at 19:02 pm.
The Auto close workflow runs at 5:00 am
@Justin_Workman - I know there is a gap of time, but according to the conditions the incident should be closed by 22nd Feb.
What version of the portal are you using? If you click Show History on the History tab of the incident, it should show the history.
I am not able to see full history in the portal. The history is available till the first resolved date (7th Feb). This happens in other work items also.
Kindly suggest.
Admin -- Settings -- Data Retention Settings -- History
If that is really low, your grooming is removing the history
Sounds like some task or history element is causing a display issue when it builds the json call.
Thinking special character in a workflow account or something of that effect.
The history not showing is a bug that was fixed in version 8.1.2 of the portal(PR68024).