RITM state changed to 'Closed Skipped' DescriptionCouple of RITMs have their state set to "Closed Skipped". The flows associated with the RITM is not responsible for this state change. Based on audit history of RITM, the state change is made by "System" user.CauseFrom binlog & nodelog, the transaction responsible for the state change can be identified. This transaction belongs to 'Flow Engine Event Handler' job. From the flow context list, based on the time frame of the transaction able to identify the flow that is responsible for making this state change. ResolutionThis flow contains "Update record" action performed on affected RITMs. This flow has been configured to run as "System" user. Review the flow that is responsible for making the state change on those RITM records.