Hi There,

We had a similar problem and when we analyzed the issue we found that there were two different SQL Agent Jobs with the same name assiciated with the same schedule. When we deleted those SQL Agent Jobs & Re-Created the Schedule, it solved the problem.

Hope it helps!