Hi,
We have upgraded our software, which uses flowable engine 6.2.1, to flowable engine 6.6.
Also we implemented some custom service tasks(to send job to long running image processors) and some scheduled threads that are deployed under flowable-task newly flowable-ui.
We need runtimeService for background scheduled thread to check/manage workflows/process instanceses.
To get the runtimeService we defined a class that implements Spring’s ApplicationContextAware and we get the runtime service while loading flowable-task/ui like below:
All Flowable apps are the same as before, just bundled together in one distributable, so the same should be achievable.
Can you share how you register our custom ApplicationContextAware class?
Then it most likely means the logic is executed to fast. Can you store the applicationContext and retrieve the RuntimeService when needed (when the actual logic is running)?