So here is my problem. I have a job with a list of workstations names stored in a job variable. Then using a loop I read each line and use that name to copy a file to a share on each workstation. This job has been working for several months. Yesterday I added a new task in the loop to delete older files in the share. When I went to test it. I started getting an error from the copy on the first time through the loop.
It it enters the loop, and the the first item I get back is a 1, then in the second time around I get the first name in the list.
So to check things, I've added and removed names from the list and I still get the 1 first, then the updated list. So the job variable updates are being read by the job. I even tried making the list blank and I still get a 1, then nothing since the list is blank. Next I tried making a new job variable and having the loop read that. Same result.. So I tried removing the loop and recreating it. Same result.
What am I missing?

I am quite sure this is a bug in an older version. This was fixed in 9.2.5.

---

Well we are on 9.1, so i'll see about getting it upgraded.

Thanks.

Since this server has about 500 jobs that run multiple times a day, would there happen to be a way to export the schedule of all the jobs? Or some way to find a time when no jobs would be running so I can take it down and upgrade it?

I usually just 'ungroup' all jobs [Interface tab - Ungroup Jobs] then sort by 'Next Run'

Then look for big gaps

This works for jobs that run once or twice a day but anything that you have running at set, short intervals will be tough to find since you are only looking at next run and not all runs.

I have a system where I put certain keywords in the description to find theses types of jobs easier but it still takes a bit of work to find a gap.

Once you find a block of time that looks viable you could try Tools Tab then Calendar. Zoom into that gap of time you think might work and see if there are short interval jobs there.

Ideally you would always have a maintenance window available where no jobs run. You would have to do this manually through the process of setting up jobs. Just tell people "We do not run jobs between 2 and 3 pm on Saturdays" or whatever time makes sense for you. The you can be comfortable using that block of time to do anything you want.

To close the loop on this. I upgraded the system this morning and no strange 1 in the loop.

Thanks for all the assistance.

To close the loop on this. I upgraded the system this morning and no strange 1 in the loop.

Thanks for all the assistance.

Thanks for confirming!

---