Error when the flow Update Record: java.util.ConcurrentModificationException Issue When running the flow, sometimes will get error failed with error: java.util.ConcurrentModificationException when the flow Update Record This problem happens randomly. Every time it happens, the error message is similar and also happens during update record. This is the error message we get when viewing the flow error: Operation(Catalog Item - Access to PowerBI.e4403d3c1b532410c8576359bc4bcbd4.5ad05916c31332002841b63b12d3ae63) failed with error: java.util.ConcurrentModificationExceptionat java.util.ArrayList$Itr.checkForComodification(ArrayList.java:911)at java.util.ArrayList$Itr.next(ArrayList.java:861)at com.glide.glideobject.Journal.insertOrUpdateEntries(Journal.java:473)at com.glide.glideobject.Journ...ErrorFlow Designer: Operation(Catalog Item - Access to PowerBI.e4403d3c1b532410c8576359bc4bcbd4.5ad05916c31332002841b63b12d3ae63) failed with error: java.util.ConcurrentModificationExceptionat java.util.ArrayList$Itr.checkForComodification(ArrayList.java:911)at java.util.ArrayList$Itr.next(ArrayList.java:861)at com.glide.glideobject.Journal.insertOrUpdateEntries(Journal.java:473)at com.glide.gl... Steps to reproduce: Create a flow trigger on service catalog.Create step to update record on sc_request table which triggered item associated to. Set requested for field to triggered request item request_for field. Attach this flow to a service catalog item.Create a new Service catalog item 3) defined. Sometimes the error will present as ConcurrentModificationException like mentioned above. CauseThis is due to when a RITM is created, a request would be created under sc_request, then a workflow will be triggered. When flow runs Update record on sc_request table, the related record is still in creating process. So those two processes are trying to update the same records, then cause concurrentmodification error as mentioned. When this happens, two workflow content will be triggered for same request. One is created by the user who raised the request item, which is expected. Another one is created by system, which was triggered by the flow update step, which is incorrect.ResolutionAdd timer before the Update record step to avoid conflict with sc_request/workflow creation. Request_for field has been populated when sc_request is created, so reapplying the field again is not needed.