Sorry for the all issues. This is BUG in 4.0. which is fixed in 4.0.1 Please use this to solve the issue. It is minor configuration setting that will help you fix the issue :- Please update the \WEB-INF\js.quartz.propertiesorg.quartz.jobStore.clusterCheckinInterval = 15 minExplanation:-This value sets the interval(from start time of executing job) at the end ofwhich the recover job will fire. It is very import in the case of clustering:Ifjob will failed on the one cluster node(For example in the case of applicationstopped on the node) then it will be successfully recovered on the othernode(per clusterCheckinInterval).I increased this value to 15 min because for complex report(time executing isbig) time of job executing will be able more than 10 min and then recoveringjob will result the problems (such as in bugs#22057, 22045, 22058). So, for cutomer we will documented it and in additionally:"..When you have smaller or bigger executing report time than 15 you willdecrease or increase appropriately this value for correct job recoveringwork.." [/code] hope it helps, Ramnik Kaur Senior QA Engineer