I have edited different items on a report caster job that was scheduled to Never run again, but then saving those changes submitted the job to run. My job was scheduled to run once on the 10th of the month and then never again. After it had run, I made a change to the job and saved that change. I didn't submit the job to run again, but it was run and output was distributed. Has anyone else had this happen?

Bethany

It happens all the time. Try just pressing the OK button instead of the Apply button when you are done with your changes and see if that helps the situation at all.

I did use the OK button and not the Apply button. Another weird thing about this is that we also made the same edits on several other jobs on the same day and only the jobs that were scheduled to run on January 10th (and never run again) are the only ones that were submitted to run again. Other jobs that were scheduled for the 10th of a previous or subsequent month were changed the exact same way and did not get resubmitted after saving the changes.

I've seen this as well and there are several posts regarding this issue. You would think that this would have been fixed by now since it's been around for ages!

My solution which seems to work pretty consistently is that if I absolutely do not want a job to run immediately, I uncheck the "Enabled" box on the main tab, make changes, and then OK/Apply. THEN, I go back in and enable it.

If it really doesn't matter if it runs, I don't worry about it and like you say, sometimes it runs, sometimes it doesn't

Thanks for the tip Darin. I was going to try disabling the job as well. I just hope that when I enable the job again it won't submit it to run immediately. Have you seen that happen?

Also, If you make your changes - hit Apply...and then X out of the screen instead of OK - it will not run.

If I only changed the Enabled box, I have never (yet) seen it submit immediately. That is why I stuck to that process.

Thanks again for your help.

Well, I painstakingly followed the prescribed measures when changing a job originally scheduled for Jan. 10, 2009 and NEVER scheduled to run again, and alas it was submitted and distributed again.

I don't know what else there I can do.

Was the schedule disabled when you made and saved the changes? or was it enabled and just set to not run again in the future?

Did you try Xing out?

We have had the same problem in 7.1, the solution mentioned above (X) worked well.
In 7.6 I think it is no mare a problem, but the X thing has become a habit.

I used the Apply button and the X and disabled the job before making changes. Then went back in enabled the job, clicked apply and then closed with the X. I probably changed 25 jobs with this same method and the only one that was submitted again was the one that was scheduled for Jan 10, '09 and to never run again.

We are moving to 7.6 sometime next month so I hope this problem is resolved in that version.

Bethany,

My guess is that this won't be fixed in v7.6.

I don't have ReportCaster access right now, but if I remember correctly, for jobs that are not to run, make your changes, disable the job AND change the next run date (I'm not sure of the exact terminology) to some time in the future - I think this ensures the job won't run.