Is this not simply a case of the backup remaining "queued" waiting for a job slot, i.e. resource on a tape drive, before going "active"?
You could increase the "priority" of the policy that is being used, and force your backups to take the first available slot.
Also, if you are used mixed retentions across policies, then it is possible that your backups only run when a tape drive becomes free.
Are you using mixed retentions? Multi-plexing?