This job normally runs every minute and I do not have any conflicting jobs in a 'Processing' state. What else could cause this?
Restarting the BG services did the trick for us.
"Waiting" means the job wants to run, but can't because of a conflict - but since you say there is no conflict then that sounds strange.
Have you tried restarting the BG service? (assuming that nothing else is running)
I do have a case opened with CA to do that for me. Fingers crossed.
As Dave says, this is a message that means the job is waiting for another job.
If it stays in this state though, it would mean that probably another Timeslicing job was running and then Cancelled/Deleted or service was restarted, and it thinks the job is still running.
Restarting bg should help, or else there is the solution below:
Clarity: Scheduled jobs stuck in waiting or scheduled status
Lastly, if that doesn't help, then cancelling and deleting that job and all other Timeslicing instances might help too, with bg restart. You may have to manually recreate your Timeslicing job schedule, so please keep note of the schedule.
Hope this helps
Retrieving data ...