# Generation of executionId

**URL:** <https://forum.flowable.org/t/generation-of-executionid/4871>\
**Category:** Flowable Engine\
**Created:** [November 14, 2019, 10:39am UTC](https://forum.flowable.org/t/generation-of-executionid/4871 "2019-11-14T10:39:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![digenn](https://avatars.discourse-cdn.com/v4/letter/d/0ea827/32.png) [@digenn](https://forum.flowable.org/u/digenn)\
**Post date:** [November 14, 2019, 10:39am UTC](https://forum.flowable.org/t/generation-of-executionid/4871/1 "2019-11-14T10:39:33Z")

</div>

Hello,  
I have a situation to expose:  
I have a commission approval task, I wish I could approve (then complete the task) one commission at a time. The goal is to continue to the next task with an executionId that makes that flow unique, and to go back to the same approval task with a new executionId. I need the executionId to always distinguish with precision in which flow I am, because obviously on the database every flow will have its data.

How can this be done?

I tried to go back simply, but apparently there is not a rule defined for which executionId continues to the completion of the task. Sometimes I find that to continue the flow is the executionId of the “Approve” task, other times the executionId which continues changes, and remains the same in the new execution of “Approve”.

 ![Cattura](https://canada1.discourse-cdn.com/flex035/uploads/flowable/original/2X/9/9671c99db79e474d108fbd55cff0f587f6596589.png)

---

<div class="post-metadata">

**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\
**Post date:** [November 20, 2019, 8:51am UTC](https://forum.flowable.org/t/generation-of-executionid/4871/2 "2019-11-20T08:51:53Z")

</div>

Have you looked at multi-instance ([https://flowable.org/docs/userguide/index.html#bpmnMultiInstance](https://flowable.org/docs/userguide/index.html#bpmnMultiInstance)). A sequential multi instance user task based on a collection sounds pretty much what you’re looking for.