# Bigexec running for a few seconds

**URL:** <https://discourse.nodered.org/t/bigexec-running-for-a-few-seconds/10360>\
**Category:** General\
**Created:** [19 April 2019 14:36 UTC](https://discourse.nodered.org/t/bigexec-running-for-a-few-seconds/10360 "2019-04-19T14:36:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nazHossain0316](https://avatars.discourse-cdn.com/v4/letter/n/9fc348/32.png) [@nazHossain0316](https://discourse.nodered.org/u/nazHossain0316)\
**Post date:** [19 April 2019 14:36 UTC](https://discourse.nodered.org/t/bigexec-running-for-a-few-seconds/10360/1 "2019-04-19T14:36:36Z")

</div>

Hello everyone. Im new to Node Red and came across an issue when using the bigexec node to trigger a batch file. I found that even when the node is done running all of the commands in the batch file, it sort of hangs with a 'running for a few seconds' message visible under the node. Based on the way my flow is set up, I feed the bigexec different arguments each time the flow is triggered. the problem is that the bigexec node just hangs and wont do anything with subsequent triggers (until i re-deploy my flow again).

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [19 April 2019 14:58 UTC](https://discourse.nodered.org/t/bigexec-running-for-a-few-seconds/10360/2 "2019-04-19T14:58:23Z")

</div>

The bigexec node is one written by a community member (you can see by the contrib part of the name)

If you look at the node at [https://flows.nodered.org/node/node-red-contrib-bigexec](https://flows.nodered.org/node/node-red-contrib-bigexec)

you can follow a link to the github page where you can open an issue direct with the author