that's it. I have 2 jobs that are scheduled to run every day at 5 am. Today we noticed that they're running twice, even though they're supposed and configured to run only once. The same happens if we "Execute Now" from the schedule list.
We forced it to make a simple/dumb check by checking and creating a "running" file, so the second time won't run if the first is still active... but this is clearly a bug. My two doubts are: no one ever faced this problem? I couldn't find anything about it (here, on the old forums and on stackoverflow). And I can't seem to find anything wrong that could point me to what's causing this behaviour, any leads?