# Outputs.influxdb did not complete within its flush interval - means points get lost

**URL:** <https://community.influxdata.com/t/outputs-influxdb-did-not-complete-within-its-flush-interval-means-points-get-lost/38862>\
**Category:** Telegraf\
**Tags:** telegraf\
**Created:** [October 22, 2024, 2:43pm UTC](https://community.influxdata.com/t/outputs-influxdb-did-not-complete-within-its-flush-interval-means-points-get-lost/38862 "2024-10-22T14:43:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Giovanni\_Luisotto](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/giovanni_luisotto/32/4017_2.png) [@Giovanni\_Luisotto](https://community.influxdata.com/u/Giovanni_Luisotto)\
**Post date:** [October 22, 2024, 2:43pm UTC](https://community.influxdata.com/t/outputs-influxdb-did-not-complete-within-its-flush-interval-means-points-get-lost/38862/1 "2024-10-22T14:43:18Z")

</div>

I’m using a telegraf Gateway to write to InfluxDB (v1), there is a warning occasionally popping up in the log, but I’ve always thought nothing of it…

```auto
{...} W! [agent] ["outputs.influxdb"] did not complete within its flush interval

```

Now, after quite some time turns out this “warning” means I’m losing data…  
I’ve “fixed” the issue by adjusting`flush_interval` and `batch_size`, still I don’t like the idea of losing data due to something that I’d compare to a timeout  
Is there a configuration to put those data back in the buffer and write them in the next interval?

---

<div class="post-metadata">

**Author:** ![srebhan](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/srebhan/32/8572_2.png) [@srebhan](https://community.influxdata.com/u/srebhan)\
**Post date:** [October 31, 2024, 2:06pm UTC](https://community.influxdata.com/t/outputs-influxdb-did-not-complete-within-its-flush-interval-means-points-get-lost/38862/2 "2024-10-31T14:06:51Z")

</div>

@Giovanni_Luisotto please report a bug and specify a way to reproduce the issue. Usually the output should put the metrics back into the buffer if it can’t send it, however as the buffer-size is limited it might overflow and thus loose data…
