# Csv reports timing out despite size of the report being too small

**URL:** https://discuss.elastic.co/t/csv-reports-timing-out-despite-size-of-the-report-being-too-small/380384
**Category:** Kibana
**Created:** [July 23, 2025, 12:57pm UTC](https://discuss.elastic.co/t/csv-reports-timing-out-despite-size-of-the-report-being-too-small/380384 "2025-07-23T12:57:33Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Ananth\_Balasubramani](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ananth_balasubramani/32/144290_2.png) [@Ananth\_Balasubramani](https://discuss.elastic.co/u/Ananth_Balasubramani)
#### Post date: [July 23, 2025, 12:57pm UTC](https://discuss.elastic.co/t/csv-reports-timing-out-despite-size-of-the-report-being-too-small/380384/1 "2025-07-23T12:57:33Z")

</div>

Reporting job status doesn't seem to get updated with status as completed and times out with maximum of 3 attempts despite Kibana generating logs: finished generating, total size in bytes: , CSV: Worker completed: \<job\_id\> etc. There are no error logs printed after the log: finished generating, total size in bytes: is printed giving any clue why the reporting index is not getting update with the right completed status. Kibana version used is 6.8.23. Any pointers to identify root cause would help

---

<div class="post-metadata">

### Author: ![Tortoise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tortoise/32/147587_2.png) [@Tortoise](https://discuss.elastic.co/u/Tortoise)
#### Post date: [July 24, 2025, 3:01am UTC](https://discuss.elastic.co/t/csv-reports-timing-out-despite-size-of-the-report-being-too-small/380384/2 "2025-07-24T03:01:10Z")

</div>

Hello @Ananth_Balasubramani

Welcome to the community!!

The Kibana version 6.8.23 is an older version. Also was the reporting working in your environment & stopped suddenly or it works intermittently or it never worked in past?

Still looking at the issue you are facing could you please review below threads if it can be of any use :

> [@Kibana 6.8.23 CSV reporting is always failing](https://discuss.elastic.co/t/kibana-6-8-23-csv-reporting-is-always-failing/316626/5):
>
> Hi @Sarat_Khilar How much RAM did you allocated to your Kibana instance? For reporting it must be at least 2Gb and failing report can happen when there is not enough memory. Please also check our troubleshooting guide: Regards, Dima

> [@Kibana Reporting -csv download fails frequently with error 'Unable to generate report Max attempts reached (3)'](https://discuss.elastic.co/t/kibana-reporting-csv-download-fails-frequently-with-error-unable-to-generate-report-max-attempts-reached-3/278405):
>
> Hello, I have tried to generate csv files using saved search on Kibana dashboard. This is downloading proper file for few cases and failing in some cases. This failure does not looks due to the size issue. I could see only text 'Unable to generate report Max attempts reached (3)' on the Reporting page. Could not find any hits to this issue from kibana logs. I have tried to download csv on different ways likeby increasing data size , applying filter etc. and getting result in sometime. Kiba…

Thanks!!

---

<div class="post-metadata">

### Author: ![Ananth\_Balasubramani](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ananth_balasubramani/32/144290_2.png) [@Ananth\_Balasubramani](https://discuss.elastic.co/u/Ananth_Balasubramani)
#### Post date: [July 26, 2025, 1:09am UTC](https://discuss.elastic.co/t/csv-reports-timing-out-despite-size-of-the-report-being-too-small/380384/3 "2025-07-26T01:09:39Z")

</div>

Sufficient memory has been allocated and the allocated memory is not even 60% utilized.
