The job splits into two sets of tasks when it runs depending on which trigger starts it, I've added a delay of two minutes to one of the sets of tasks to stop the clashing. The log does report though that the job started twice at the same time, so this is definitely a bug.