Eazyby time out problem 720 seconds

[Cristian Zuccalá]

Summary: The problem is based on the large volume of information that is handled and the lack of connection between the points that end up generating a time out error in the production environment. keep in mind that there is no intention of adding new fields to make the links.
Attached error, I don't know if it happened to someone that it took so long to resolve, I have an updated Jira server just like the eazybi

[Zane eazyBI Support · Accepted solution]

Hi @Cristian Zuccalá ,

The main reason for timeout errors is complex reports with large data amounts. You may increase the query timeout to 720 seconds (12 minutes) which is quite a lot. Please note  that the timeout limit works as a safeguard to protect eazyBI and server where it is installed from resourceful or never-ending requests caused by massive or poorly built reports. Please consider reducing the limit for the timeout for up to a few minutes (https://docs.eazybi.com/eazybijira/set-up-and-administer/set-up-and-administer-for-jira-server/advanced-settings#Advancedsettings-Increasequerytimeout).

We always suggest checking out if there is a room for the report optimization as well.
You may send a report definitions to eazyBI Support (support@eazyBI.com) for inspection. There is a short instruction on how to get report definition: https://docs.eazybi.com/eazybijira/analyze-and-visualize/create-reports#Createreports-Exportandimportreportdefinitions

Quick tip. From the screenshot, I can see that option Nonempty is disable. Please, enable option Nonempty to increase report performance and remove cycles that are not related to the selected Project or Epic (https://docs.eazybi.com/eazybijira/analyze-and-visualize/create-reports#Createreports-Pagedimensions)

Zane / eazyBI@support.com
Best,

[Cristian Zuccalá]

Thanks Zane, I'll try those options