# Receive Task: How to continue the process?
**URL:** https://forum.flowable.org/t/receive-task-how-to-continue-the-process/625
**Category:** Flowable Engine
**Created:** [June 7, 2017, 7:34am UTC](https://forum.flowable.org/t/receive-task-how-to-continue-the-process/625 "2017-06-07T07:34:38Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Martin](https://forum.flowable.org/u/Martin)
#### Post date: [June 7, 2017, 7:34am UTC](https://forum.flowable.org/t/receive-task-how-to-continue-the-process/625/1 "2017-06-07T07:34:38Z")
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
---
### Author:  [@joram](https://forum.flowable.org/u/joram)
#### Post date: [June 7, 2017, 7:40am UTC](https://forum.flowable.org/t/receive-task-how-to-continue-the-process/625/2 "2017-06-07T07:40:11Z")
.signal() has been renamed to .trigger() (see [http://www.flowable.org/docs/userguide/migration.html#\_signaling\_an\_execution](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](https://github.com/flowable/flowable-engine/commit/7d6b7716a8031aa41d7d8d0551df1e523d7ac747)
---
### Author:  [@Martin](https://forum.flowable.org/u/Martin)
#### Post date: [June 7, 2017, 11:56am UTC](https://forum.flowable.org/t/receive-task-how-to-continue-the-process/625/3 "2017-06-07T11:56:38Z")
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)
---
### Author:  [@joram](https://forum.flowable.org/u/joram)
#### Post date: [June 12, 2017, 7:53am UTC](https://forum.flowable.org/t/receive-task-how-to-continue-the-process/625/4 "2017-06-12T07:53:24Z")
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](https://github.com/flowable/flowable-engine/commit/42f588d16cdd9d2c1a4b8c3ab282f9920540c2dc)
---
### Author:  [@sagaraa](https://forum.flowable.org/u/sagaraa)
#### Post date: [November 22, 2018, 7:35am UTC](https://forum.flowable.org/t/receive-task-how-to-continue-the-process/625/5 "2018-11-22T07:35:29Z")
how did you get the child execution id
name the API, that will be helpful