AnsweredAssumed Answered

Queries from 'start' executionListener on first user task.

Question asked by jenguran on Feb 4, 2011
Latest reply on Jun 19, 2014 by trademak
I have a process that goes:
start-> manual task -> user task -> exclusive gateway -> stuff that doesn't matter -> end.
I've put a "start" event execution listener on the first user task. The problem I'm having is, the engine doesn't seem to persist anything until some point past that listener being called. So if I try to query the runtime or history services in my listener, nothing is found. On all the user tasks after the first one I can query for everything.

It looks to me like the thread that starts the process instance runs through the process until it stops at the first wait state. At that point everything is persisted, but the start executionListener has already been called. Is that something that's intended, or could it persist everything and then call the listeners?

My apologies if this has already been asked, I couldn't find anything related to it.