# Logstash record\_last\_run updated on output issue **URL:** \ **Category:** Logstash\ **Created:** [July 13, 2021, 3:38pm UTC](https://discuss.elastic.co/t/logstash-record-last-run-updated-on-output-issue/278570 "2021-07-13T15:38:51Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![spawnrider](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spawnrider/32/91583_2.png) [@spawnrider](https://discuss.elastic.co/u/spawnrider)\ **Post date:** [July 13, 2021, 3:38pm UTC](https://discuss.elastic.co/t/logstash-record-last-run-updated-on-output-issue/278570/1 "2021-07-13T15:38:51Z")
Hi, Why Logstash (JDBC input plugin) is recording the "Record Last Run" timestamp in the metadata file even if there is an issue on the output ? I had an connection issue (due to network) to the Elasticsearch instance but the last run timestamp is updated for my pipeline. Is there any way to do avoid this ? Regards, Yohann ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [July 13, 2021, 5:10pm UTC](https://discuss.elastic.co/t/logstash-record-last-run-updated-on-output-issue/278570/2 "2021-07-13T17:10:21Z")
> [@spawnrider](#): > > Is there any way to do avoid this ? Inputs send events to the pipeline and their responsibility ends there. You could try configuring [persistent queues](https://www.elastic.co/guide/en/logstash/current/persistent-queues.html), which try to ensure that data in the pipeline is delivered to the output. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 10, 2021, 5:11pm UTC](https://discuss.elastic.co/t/logstash-record-last-run-updated-on-output-issue/278570/3 "2021-08-10T17:11:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.