I have a report that an application runs a few hundred times a day. The data is specific to the individual running the report. There are only two parameters and they are populated by the application and the report is rendered posting a reportserver URL. The report renders in 5 seconds. Today I noticed this report running past the 30 minute execution timeout limit we have set. We have seen this behaviour before. The only way we found to stop the report from continueing to run is to cycled the SSRS service. Today I looked at the Running jobs table in the SSRS database and the Timeout was registering -1. I assume this means the report will run until the end of time or the next round of MS security patches. ( LOL ) I have noticed that if a report has an execution timeout set, the value that it is set for is what is shows up in that column. If it is not set the timeout vaue is the value set at the system level. I have asked the developer (not the original developer) who maintains this application and they do not know why it is showing up as a -1. Is there a way to control the timeout of this report when it is rendered? We are using SSRS 2008. We are on SP2, CU2.