BAQ Timeout error?

Hi,
I have a report Crystal report i wrote before in Epicor 9 that carried over to E10. Everything was working fine in E10. but now when i try to run the report, i am getting this error below. The report is based of BAQ i wrote.

BAQ execution returned errors:
Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Any idea how i can resolve this issue?

Try limiting the scope of the data either within the BAQ or the report itself. It seems you have more data then the BAQ can handle.

I would test the BAQ itself with some kind of filter that would limit the data to prove it works then go from there.

The BAQ itself works without any filters (takes some time but still works).

Query returned 810 row(s).
Query has no more records to return.
Query execution total time: 46612.9083 ms.

I have the BAQ execution setting as:

Sorry to necro an old post, but I was having this issue in 10.2 and googling brought me here, so I figured I’d post what I found for future seekers.

My query was timing out at 30 seconds. Both when executing it in the BAQ Designer as well as through the oData link calling my BAQ. My queryTimeOut setting was also set to 0 by default. I set the value to 60 and saved the BAQ, and then my BAQ started working–showing it was taking 38 seconds to execute.

I’m guessing the queryTimeOut was inheriting 30 seconds from another setting somewhere, regardless of being set to 0 (which I would interpret as unlimited) and only by changing this value to an explicit number caused it to override that inherited value.

4 Likes

Thank you Lee. This gives me a starting point to try and fix our BAQ issue.