Eazybi Query execution timeout of 60 seconds reached

Ioannis Kouris June 14, 2023

Hello,

I am trying to create a report in Eazybi with 2 calculated measures.

The first is already imported by Eazybi and it's called Issues with Event Log Time which counts the number of tickets with that field filled out.

The second measure is calculating the average time between the Event log time field and the ticket resolution date.

I have 3 dimensions in pages and 1 dimension in rows which is called Priority.

eazybi.jpg

My problem is that i get the "Query execution timeout of 60 seconds reached" when i try to load the report with the Priority dimension expanded but it loads fine if it is not.

Is there a way to resolve this problem?

Thank you

 

1 answer

0 votes
Lauma Cīrule
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 14, 2023

Hi @Ioannis Kouris,

Probably the problem is with the Avg calculation. Could you please provide the formula here or to support@eazybi.com?

Lauma / support@eazybi.com

Ioannis Kouris June 15, 2023

Hi Lauma,

Thanks for looking into this.

I was trying with 2 different formulas

1.  AVG(
Filter(
Descendants([Issue].CurrentMember, [Issue].[Issue]),
NOT IsEmpty([Measures].[Issue Event Log Time])
),
CASE WHEN
[Measures].[Issues resolved] > 0
THEN
DateDiffMinutes([Measures].[Issue Event Log Time],
[Measures].[Issue resolution date]
)
END
)


2. AVG(
Filter(
Descendants([Issue].CurrentMember, [Issue].[Issue]),
DateInPeriod([Issue].CurrentHierarchyMember.get('Resolved at'),
[Time].CurrentHierarchyMember) AND
([Measures].[Issues created],
[Time].CurrentHierarchy.DefaultMember) > 0
),
DateDiffMinutes(
[Measures].[Issue Event Log Time],
[Issue].CurrentHierarchyMember.get('Resolved at'))
)

Lauma Cīrule
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 16, 2023

Hi @Ioannis Kouris ,

Thanks for the follow-up! Unfortunately, the Descendants function can be resource costly if there are many issues in the cube. A custom calculation of minutes between the dates for resolved issues during the import might be the best solution; see more here https://docs.eazybi.com/eazybi/data-import/data-from-jira/jira-custom-fields/new-calculated-fields or contact support@eazybi.com if you need assistance with creating a JavaScript custom field for this case.

Still, there is one more thing you might try combining the first and second formula (filtering properties first has proven to be more efficient in some cases than filtering by measures):

Avg(
Filter(Descendants([Issue].CurrentMember, [Issue].[Issue]),
DateInPeriod(
[Issue].CurrentHierarchyMember.get('Resolved at'),
[Time].CurrentHierarchyMember
) AND
NOT IsEmpty([Measures].[Issue Event Log Time]) AND
[Measures].[Issues resolved] > 0
),
DateDiffMinutes(
[Measures].[Issue Event Log Time],
[Issue].CurrentHierarchyMember.get('Resolved at')
)
)

Lauma / support@eazybi.com

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events