org.hibernate.LazyInitializationException

Which IIQ version are you inquiring about?

8.3

Please share any images or screenshots, if relevant.

Share all details about your problem, including any error messages you may have received.

2026-04-20 15:48:42,546 TRACE https-jsse-nio-443-exec-9 sailpoint.WorkflowTrace:217 - Wait timeout until : null
2026-04-20 15:48:42,546 TRACE https-jsse-nio-443-exec-9 sailpoint.WorkflowTrace:217 - Backgrounding step Waiting for Owner Approval
2026-04-20 15:48:42,578 ERROR https-jsse-nio-443-exec-9 sailpoint.api.Workflower:3379 - Exception during final save of task result
sailpoint.tools.GeneralException: org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: sailpoint.object.IdentityRequest.items, could not initialize proxy - no Session

at sailpoint.persistence.HibernatePersistenceManager.commitTransaction(HibernatePersistenceManager.java:586) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.persistence.ClassPersistenceManager.commitTransaction(ClassPersistenceManager.java:211) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.server.InternalContext.commitTransaction(InternalContext.java:601) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.api.Workflower.suspendCase(Workflower.java:3376) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.api.Workflower.advance(Workflower.java:4591) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.api.Workflower.assimilate(Workflower.java:4213) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.api.Workflower.handleWorkItem(Workflower.java:7651) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.api.Workflower.process(Workflower.java:1858) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.api.Workflower.process(Workflower.java:1882) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.api.WorkflowSession.advance(WorkflowSession.java:468) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.service.WorkflowSessionService.advance(WorkflowSessionService.java:105) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.service.form.FormService.next(FormService.java:188) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.service.form.FormService.submit(FormService.java:111) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.rest.ui.form.BaseFormResource.submitOrValidate(BaseFormResource.java:162) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]
at sailpoint.rest.ui.form.BaseFormResource.submit(BaseFormResource.java:122) ~[identityiq.jar:8.4p3 Build 30f52882581-20250902-165538]

Anyone has any idea about this error

This error basically means that you are trying to access a resource which has already been decached. Please check your custom code for any decache statements and check the step as well which resource it is trying to access.

@akshay1

Can you please share the piece of code from where you are getting this error ?

It can also be thrown if you try to access an object that was originally loaded with a transaction that has been closed before. Some steps in a workflow will do this. Any object that was loaded before might not be immediately usable afterwards.

A simple fix in these cases is often to reattach the object in question. ObjectUtil.reattach() may be used here.

@akshay1 Are you having any customization related to identity requests? If yes, could you please share it here.

hi @akshay1

is this error your getting for Active Directory application provisioning/Deprovisioning?

This issue has been resolved, Created one more step and in that step i put “wait”, So it will wait for PM task to push forward and this resolved my issue