I have a process containing an user task on which an interrupting timer boundary event is attached to.
No matter if a timeout is triggered or not, later in the process flow, both “paths” will arrive to the same Service Task.
In the Java Delegate class of this service task I’m accessing the user id of the current authenticated user via:
ProcessEngines.getDefaultProcessEngine() .getIdentityService() .getCurrentAuthentication() .getUserId();
Now here is my issue:
In case the user task gets completed properly, I’m able to retrieve the user id.
But if the timeout is triggered on the user task the method
I don’t get any logs related to this issue, just the service which requires the user id fails.