# "The flows on the server have been updated" with Pi gpiod nodes

**URL:** https://discourse.nodered.org/t/the-flows-on-the-server-have-been-updated-with-pi-gpiod-nodes/29827
**Category:** General
**Created:** [10 July 2020 07:22 UTC](https://discourse.nodered.org/t/the-flows-on-the-server-have-been-updated-with-pi-gpiod-nodes/29827 "2020-07-10T07:22:34Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![Charry2014](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/charry2014/32/46308_2.png) [@Charry2014](https://discourse.nodered.org/u/Charry2014)
#### Post date: [12 July 2020 07:57 UTC](https://discourse.nodered.org/t/the-flows-on-the-server-have-been-updated-with-pi-gpiod-nodes/29827/8 "2020-07-12T07:57:41Z")

</div>

Many thanks for the replies. First let's deal with the Docker thing here - Docker is likely not the problem here, at least not alone. The cause in the previous issue ([read it here](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/60)) was one of the nodes misbehaving and here too if I remove the Pi GPIO nodes then the whole problem goes away. I will build a test outside Docker which will be interesting anyway but Docker images are not so mysterious.

---

_[View the full topic](https://discourse.nodered.org/t/the-flows-on-the-server-have-been-updated-with-pi-gpiod-nodes/29827)._