# Batch InfluxDB CLI

**URL:** <https://discourse.nodered.org/t/batch-influxdb-cli/32982>\
**Category:** General\
**Tags:** database\
**Created:** [17 September 2020 06:43 UTC](https://discourse.nodered.org/t/batch-influxdb-cli/32982 "2020-09-17T06:43:02Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [17 September 2020 07:26 UTC](https://discourse.nodered.org/t/batch-influxdb-cli/32982/4 "2020-09-17T07:26:31Z")

</div>

Rather than your suggested solution could you just queue up messages until the server recovers? Assuming that you can catch the error (you should be able to use a Catch node) then the solution in this thread might solve the problem without a major restructring of your system. [How to queue / hold the sensor values ,when there is a internet failure occurs](https://discourse.nodered.org/t/how-to-queue-hold-the-sensor-values-when-there-is-a-internet-failure-occurs/32608/15)

As a matter of interest, why have you got multiple influx nodes?

---

_[View the full topic](https://discourse.nodered.org/t/batch-influxdb-cli/32982)._