ddelsignore

Thanks Mike, that's exactly what we've done. I appreciate the response!

Hi all, I've got an 8.2 community server and a 9.0 commercial license. Single server instance, no customizations. I'm doing a fresh install of the server on a new instance and importing the database to a new cluster. The v9 upgrade docs say: The only commercial downloads available are 8.0.4 and 9.0.0. Do I need to request the 8.2.0 commercial installer so I can upgrade? Or can I use the 8.0.4 install to upgrade from community to commercial? Or can I just upgrade directly from 8.2.0 community to 9.0 commercial? (This worked fine in a test environment). Thanks!

@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).

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?