Job triggered twice?

Any report of a Job being triggered more than once. I have a Job set up yo run at 5 after every hour asynch. For some reason it started twice just seconds apart.

11-Apr-2008 18:07:32 datablaster-at 46 reporttable extract Finish message sent.
11-Apr-2008 18:07:23 datablaster-at 46 reporttable extract Finish message sent.
11-Apr-2008 18:07:08 datablaster-at 46 reporttable extract Remote job finished.
11-Apr-2008 18:07:02 datablaster-at 46 reporttable extract Remote job finished.
11-Apr-2008 18:06:23 datablaster-at 46 reporttable extract Agent "IAT" contacted.
11-Apr-2008 18:06:17 datablaster-at 46 reporttable extract Agent "IAT" contacted.
11-Apr-2008 18:06:11 datablaster-at 46 reporttable extract Start message sent.
11-Apr-2008 18:06:02 datablaster-at 46 reporttable extract Start message sent.
11-Apr-2008 18:05:57 datablaster-at 46 reporttable extract Remote job started.
11-Apr-2008 18:05:41 datablaster-at 46 reporttable extract Remote job started.

I guess both instances waited in the queue for some time. As soon as the queue became free from running other job(s), it started these 2 job instances Because the job definition is likely set to run job asynchronous, both job instances ran concurrently.

But if they run asyncj they dont sit in any queue. When i look at the logs the 17:05 ran the 19:05 ran all the times for the rest of the day ran only once just this specific time it ran twice a few seconds apart. What you say would make sense but how did the TWO instances of this job even get in the queue? Its scheduled to run 5 aftter the hour every hour and did that every hour but this one.

Async. mode is not about job not waiting in a queue, it is about job not blocking queue while running. Every job except jobs with "on startup" schedule goes to a queue and takes position in the queue according to job priority. If the queue is busy, async jobs is going to wait starting in the queue until the queue becomes free from running sync. jobs. If you don't a job start time to depend on other jobs, you can assign it to a separate job queue. Hope it makes sense.

I do have this specific job assigned to its own queue and the jobs is set to time out after 30 minutes. Maybe im missing the big picture but I dont understand how a job scheduled to run every hour in its own queue, asynch and 30 minutes timeout could run twice just seconds apart. I made sure we dont have a time or system clock synch going on so that didnt change. I think maybe Ive had enough of the asynch option, thi sjust doesnt make sense to me.

If there are no other jobs assigned to the same queue, then my initial guess was no correct.

Still, something made it to wait in the queue or some other way delayed the start. What else do you see in the job along around the start time? Any other jobs or messages? Any heavy processing, backups on the server that made it run slow for a little while?