# Weird scrambled output of exec node using bacnet readprop command

**URL:** https://discourse.nodered.org/t/weird-scrambled-output-of-exec-node-using-bacnet-readprop-command/92994
**Category:** General
**Tags:** docker, exec
**Created:** [8 November 2024 16:58 UTC](https://discourse.nodered.org/t/weird-scrambled-output-of-exec-node-using-bacnet-readprop-command/92994 "2024-11-08T16:58:41Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [8 November 2024 18:09 UTC](https://discourse.nodered.org/t/weird-scrambled-output-of-exec-node-using-bacnet-readprop-command/92994/5 "2024-11-08T18:09:42Z")

</div>

> [@ThingsTinkerer](#):
>
> Any way to configure exec node to run sequentially and NOT in parallel?

You can force them to be sequential using [this flow](https://discourse.nodered.org/t/wait-until-node-changed-behavior-after-recent-update/92129/2).

---

_[View the full topic](https://discourse.nodered.org/t/weird-scrambled-output-of-exec-node-using-bacnet-readprop-command/92994)._