# Get history data of failure node

**URL:** <https://forum.flowable.org/t/get-history-data-of-failure-node/6077>\
**Category:** Flowable Engine\
**Created:** [May 25, 2020, 9:37am UTC](https://forum.flowable.org/t/get-history-data-of-failure-node/6077 "2020-05-25T09:37:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![zhudongdong](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/zhudongdong/32/2408_2.png) [@zhudongdong](https://forum.flowable.org/u/zhudongdong)\
**Post date:** [May 25, 2020, 9:37am UTC](https://forum.flowable.org/t/get-history-data-of-failure-node/6077/1 "2020-05-25T09:37:32Z")

</div>

Hi, Can anyone suggest is there any chance that I can get the history data when the flow node (with flowable:async = false )fails.  
I found that when the node is set to sync ,all data will be lost when the node fails,but I need the data showing whether the node fails or not. For example :

```
    <startEvent id="startEvent"/>
    <sequenceFlow sourceRef="startEvent" targetRef="someService"/>

    <serviceTask id="someService" name="" flowable:class="xxx.xxx.SomeService" flowable:async="false"/>
    <sequenceFlow sourceRef="someService" targetRef="end"/>

    <endEvent id="end">
    </endEvent>
</process>

```

In this case ,The process will fail at serviceTask, when it fails, no history data will be stored, Is there any configuration about this ?  
If not ,how could I get the history data of this failed service task?

---

<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:** [May 26, 2020, 8:48pm UTC](https://forum.flowable.org/t/get-history-data-of-failure-node/6077/2 "2020-05-26T20:48:37Z")

</div>

> [@zhudongdong](#):
>
> The process will fail at serviceTask, when it fails, no history data will be stored, Is there any configuration about this ?

The Flowable engine will move from any wait state to any other wait state. In this example, the process will run from start to end. On failure, it will rollback to the previous state (which is not started). Making the service task makes it a wait state and forces the transaction to commit.

---

<div class="post-metadata">

**Author:** ![zhudongdong](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/zhudongdong/32/2408_2.png) [@zhudongdong](https://forum.flowable.org/u/zhudongdong)\
**Post date:** [May 27, 2020, 2:29am UTC](https://forum.flowable.org/t/get-history-data-of-failure-node/6077/3 "2020-05-27T02:29:28Z")

</div>

Thanks Joram.

Do you mean I have to make the service task async in this case , and there is still no way to get the history data in sync mode,am I right?

---

<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:** [May 27, 2020, 9:03am UTC](https://forum.flowable.org/t/get-history-data-of-failure-node/6077/4 "2020-05-27T09:03:19Z")

</div>

History data, by default, is synchronous. The moment you reach a wait state, both the runtime and history data is written to the database in the same transaction.

---

<div class="post-metadata">

**Author:** ![zhudongdong](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/zhudongdong/32/2408_2.png) [@zhudongdong](https://forum.flowable.org/u/zhudongdong)\
**Post date:** [May 28, 2020, 2:50am UTC](https://forum.flowable.org/t/get-history-data-of-failure-node/6077/5 "2020-05-28T02:50:46Z")

</div>

I got it, Thanks for your reply.