reportTimeout Behavior in Async Requests

[jitendra5792]

We are currently using async reports and sending multiple asynchronous requests to jsreport. As expected, jsreport adds these requests to its queue.

We’ve configured the reportTimeout setting to 45 minutes. However, we’ve observed that the timeout countdown begins as soon as the request reaches jsreport — not when the actual report execution starts.

Ideally, we were expecting the reportTimeout to start only once the report begins execution, rather than from the time it enters the queue. Could you please confirm if this is the intended behavior? If so, is there a recommended approach to handle longer queue times without prematurely triggering the timeout?

These async reports, as well as others in the queue, failed due to the 45-minute timeout being reached. The delay was caused by earlier async reports that were still pending in the queue.

[admin]

The reportTimeout is based on when the request arrived. This was designed a couple of years ago and still works the same with no complaints so far. However, I understand this doesn't play so well with async requests.

We will reconsider this and come back shortly.
Thank you for the ideas.