ddelsignore Posted January 26 Share Posted January 26 We have a report that takes ~30 minutes to run in the UI. The report itself is only 1-2 pages of data, but is composed of a large amount of aggregate data. I'm scheduling the report to run using the /rest_v2/reportExecutions endpoint, then polling every minute to wait for the report to complete. For about 20 minutes the job has a status of "execution". After that I receive a 404 / resource.not.found response. I know what you're going to say - fix your queries. While a developer works on that, is there a way to configure the server to keep things around longer? A secondary question - where is the output of 'reportExecutions' jobs cached? Link to comment Share on other sites More sharing options...
Solution Tirupathi Mangalarapu Posted January 31 Solution Share Posted January 31 Hello There, Looks like the session is being timed out. Can you please check this KBA: And updated the session timeout accordingly and redo the same tests? Link to comment Share on other sites More sharing options...
ddelsignore Posted January 31 Author Share Posted January 31 @Tirupathi Mangalarapu That solved it, thank you! To summarize: report executions triggered by the reportExecutions REST endpoint have a maximum run time limited by the session-timeout set in web.xml (default: 20 minutes). Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now