Hourly Job Changes Next Start Time

[f0gax]

I have a job set to run hourly. It had been malfunctioning and with help from this forum I got it back on track. So starting at 5:50 PM Friday it ran every hour until Saturday when it runs at 1:50 AM and then the next job starts at 3:17 AM. The 1:50 run only took 4 minutes to complete (79 files). Then it runs at 4:17, 5;17, and 6:17 (this one runs for 30 minutes). Then it runs again at 7:27 AM and goes for 30 minutes. It then does not run again until 10:44 PM, taking about an hour to complete. And it does not run again through this morning (about 8 AM US ET).

But the job tells me it will run again at 9 something AM.

I figure maybe the profile has become corrupted or something so I disable the original profile and create a new one with the exact same parameters, and specify that it start at a specific time. When that time comes, the next start time is incremented by 9 seconds, and then when that comes 9 more seconds, and so on. After a few iterations of this it then increments by an hour.

Now I'm really confused. So I disable the new profile and enable the old one. I then set a specific next run time and wait. The same thing happens. I've since kicked it off manually to get the data copied. But this is strange.

Super Flex 5.61 on Windows Server 2008 R2.

[f0gax]

And now another job (set to run every 15 minutes) is doing the same thing.

[superflexible]

It could be that you need to allow more jobs to run at the same time. The number is specified on the Program Settings dialog, tab sheet Advanced. I recommend settings it it to 12. Otherwise, jobs will not start if a number of other jobs are already running.

The option is called "Max. simultaneous jobs".