Receive Task: How to continue the process?

Flowable Engine
1

Hello,

how can a process be continued after reaching a reveive task ?
The documentation says runtimeService.signal(…). But the signal method is not anymore available in RuntimeService.
In version 5 I used the signal method to continue.

Thanks for help.
Martin

1 Like
2

.signal() has been renamed to .trigger() (see http://www.flowable.org/docs/userguide/migration.html#_signaling_an_execution). It’s just a name change, the semantics remain the same.

I’ll check the docs and fix it, thanks.
Edit: doc updated: https://github.com/flowable/flowable-engine/commit/7d6b7716a8031aa41d7d8d0551df1e523d7ac747

3

Thanks for fast answer. Now it works.

I tried already .trigger(). My fault was that I called with an parent-execution-id. That causes an exception. You need to select the child execution.

Maybe the trigger function should handle this different than throwing an exception? (Only an idea)

This exeption is thrown:
Caused by: org.flowable.engine.common.api.FlowableException: Programmatic error: no current flow element found or invalid type: null. Halting.
at org.flowable.engine.impl.agenda.TriggerExecutionOperation.run(TriggerExecutionOperation.java:61)
at org.flowable.engine.impl.interceptor.CommandInvoker.executeOperation(CommandInvoker.java:81)
at org.flowable.engine.impl.interceptor.CommandInvoker.executeOperations(CommandInvoker.java:65)
at org.flowable.engine.impl.interceptor.CommandInvoker.execute(CommandInvoker.java:49)
at org.flowable.engine.impl.interceptor.TransactionContextInterceptor.execute(TransactionContextInterceptor.java:51)
at org.flowable.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:64)
at org.flowable.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:30)
at org.flowable.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:56)
at org.flowable.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:51)
at org.flowable.engine.impl.RuntimeServiceImpl.trigger(RuntimeServiceImpl.java:349)

4

Handling it differently is impossible, as for a complex process instance there are potentially multiple executions that could be triggered.

I did make the exception that’s being thrown (hopefully) a bit clearer in this commit: https://github.com/flowable/flowable-engine/commit/42f588d16cdd9d2c1a4b8c3ab282f9920540c2dc

5

how did you get the child execution id
name the API, that will be helpful

1 Like