Hi @joshtechsolutions,
You can set job queues to retry using Maximum No. of Attempts or even trigger them via Power Automate. But the real focus should be on why they are failing in the first place.
From experience, common causes are deadlocks or concurrency issues. For example, the job queue may be trying to process data while users are actively working, which leads to update conflicts. These are genuine system-level issues. Simply forcing the job queue to restart doesn’t solve the problem and can actually make it worse over time.
If your scenario doesn’t fall into these categories, then frequent failures are not expected. If the job queues are custom, there is likely an issue in the logic that needs to be reviewed. If they are standard, they should generally run on schedule without repeated failures, so it could be specific data causing the issue.
There’s a difference between making job queues run and making them run reliably. I’ve seen cases where job queues were failing without clear errors, and it turned out to be a Microsoft service node issue, which Support had to resolve.
Also, is the customer on On-Prem or SaaS?
Thankyou
