# Report Module Timeout

**URL:** <https://forum.inductiveautomation.com/t/report-module-timeout/102828>\
**Category:** Ignition\
**Tags:** perspective, reporting\
**Created:** [February 25, 2025, 1:40am UTC](https://forum.inductiveautomation.com/t/report-module-timeout/102828 "2025-02-25T01:40:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![monc](https://avatars.discourse-cdn.com/v4/letter/m/48db29/32.png) [@monc](https://forum.inductiveautomation.com/u/monc)\
**Post date:** [February 25, 2025, 1:40am UTC](https://forum.inductiveautomation.com/t/report-module-timeout/102828/1 "2025-02-25T01:40:13Z")

</div>

Hello All,

I sometimes seem to have an issue where the report is not fetching properly.

And when the user hits refresh, it will spawn another report execution.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/5/85651e584d99aaca0939555bf48731ac7efb9030.png)

Is there a way to configure a timeout for reports?

I tried canceling, but it looks like it's stuck.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/4/54d7085a7e3f3c06faf307cb88f068cb59eb4816.png)

Now, this will slow down the system and cause a gateway restart.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 25, 2025, 1:09pm UTC](https://forum.inductiveautomation.com/t/report-module-timeout/102828/2 "2025-02-25T13:09:03Z")

</div>

> [@monc](#):
>
> Is there a way to configure a timeout for reports?

No.

> [@monc](#):
>
> looks like it's stuck.

Yup. You should limit the timespans you can pass to your report, or perhaps analyze your DB for query performance (missing indices, in particular).

> [@monc](#):
>
> cause a gateway restart.

Yes. If you do not succeed with the limits, you may need to switch to running your report with a script, and script controls to prevent re-execution. Then you will need to use a PDF viewer instead of the Report Viewer.

You may also need more resources for gateway server and DB server.

---

<div class="post-metadata">

**Author:** ![drojas](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drojas/32/3403_2.png) [@drojas](https://forum.inductiveautomation.com/u/drojas)\
**Post date:** [March 4, 2025, 6:13pm UTC](https://forum.inductiveautomation.com/t/report-module-timeout/102828/3 "2025-03-04T18:13:38Z")

</div>

> [@pturmel](#):
>
> you may need to switch to running your report with a script, and script controls to prevent re-execution. Then you will need to use a PDF viewer instead of the Report Viewer.

I can confirm that this is a much better approach to reporting. Generate reports during a low use time (especially very long running ones) through scripting...store them as PDFs into a database, then use @pturmel Blob Server module to present the PDF into a viewer as needed. Of course this only works for pre-generated reports. If you want ad-hoc reporting on the fly...you need to control how much data to show to not take too long or bog down the system.

> [@Automation Professionals' Blob Server Module](https://forum.inductiveautomation.com/t/automation-professionals-blob-server-module/57970/1):
>
> Automation Professionals is pleased to announce an alpha release of its new Blob Server Module. Available only for Ignition v8.1, here. The Blob Server Module provides a simple way to deliver images, PDF files, or other binary content from a database to your Perspective clients or other web applications. Without needing the WebDev module. All you need is a Named Query that has appropriate security settings and returns a single row with two columns: Content, and ContentType. Modest documentati…