# Engine Locks with Intermediate Timer Catching event

**URL:** <https://forum.flowable.org/t/engine-locks-with-intermediate-timer-catching-event/9376>\
**Category:** Flowable Engine\
**Created:** [May 19, 2022, 7:28pm UTC](https://forum.flowable.org/t/engine-locks-with-intermediate-timer-catching-event/9376 "2022-05-19T19:28:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ckirk](https://avatars.discourse-cdn.com/v4/letter/c/94ad74/32.png) [@ckirk](https://forum.flowable.org/u/ckirk)\
**Post date:** [May 19, 2022, 7:28pm UTC](https://forum.flowable.org/t/engine-locks-with-intermediate-timer-catching-event/9376/1 "2022-05-19T19:28:24Z")

</div>

Hello,

New to Flowable and I just built cloned and built the latest tag (6.7.2) from Github on Windows 10. The flowable-ui app functions normally. But when I build a simple two HttpTask ([www.google.com](http://www.google.com)) process definition with a timer event between (PT1M) and run multiple copies of this script simultaneously (5 seems to be a magic number), the engine appears to lock up after the timeout. The UI app continues to function. The API continues to function but the 5 scripts never complete and I cannot start a new process instance (either with UI or API) of any process definition.

Have tried this with both H2 and MySql as databases.

I see the jobs present in the ACT\_RUN\_TIMER\_JOB table and then disappear from that table after the timeout but they do not “complete”. As I said, also cannot start another process instance. A bit stuck here as I’m not familiar enough yet with the code. Any thoughts?

Thanks in advance,  
//Chris

---

<div class="post-metadata">

**Author:** ![filiphr](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/filiphr/32/315_2.png) [@filiphr](https://forum.flowable.org/u/filiphr)\
**Post date:** [August 17, 2022, 9:59am UTC](https://forum.flowable.org/t/engine-locks-with-intermediate-timer-catching-event/9376/3 "2022-08-17T09:59:08Z")

</div>

Hey @ckirk,

I believe that you are affected by the same problem as I’ve described in [Parallel multi-instance subprocess not working - #4 by filiphr](https://forum.flowable.org/t/parallel-multi-instance-subprocess-not-working/7236/4).

We are currently aware about this problem and are working on a potential fix for it.

Cheers,  
Filip