Microsoft Dynamics 365 | Integration, Dataverse...

Why failed async workflow show as waiting?

(0) Share

Report

Posted on by Ning Zhu

162

We just recently noticed that tons of async workflows should be just failed due to various reasons, such as the base record deleted before the workflow can finish.

However, those are showing as "Waiting" and in several thousands.

Could someone explain why those workflows are not marked as "Failed" but still "Waiting"?

Also, our async server is crashed recently, we try to see what are impacts if there are more than 5,000 async workflows are marked as "waiting" inside the system.

Thanks a million!

All responses (2)

Answers (0)

Leah Ju Microsoft Employee on at

Like (0)

Report

RE: Why failed async workflow show as waiting?

Hi Ning,

Have you checked the workflow owner?

If the owner of the workflow is not licensed, and hence the jobs are struck in waiting status.

If so, please proceed to provide license and role to the owner of the workflow, and then proceed to bulk resume the jobs.

Also, you need contact Microsoft Support Team because it's probably an error in their servers, that stuck you processes:

Get Help + Support - Dynamics | Microsoft Docs
Suggested answer

Mohamed GRAIB 2,498 Super User 2024 Season 2 on at

Like (0)

Report

RE: Why failed async workflow show as waiting?

Hi Ning,

I think that a failed asynchronous workflow can appear as "waiting" because the workflow is still in the process of running, even though it has failed. This is because when the encounters an error, it is unable to complete and is left in a "waiting" state until it can be resolved.

Also the Async Timeout setting in Dynamics 365 can also cause async workflows to be stuck in a "waiting" state if the workflow takes longer to complete than the specified timeout.

So to prevent these errors, I suggest to :

- the workflow history and the system logs for any errors that may have occurred. This can help you identify the root cause of the issue and take appropriate actions to resolve it.

- Check the Workflow dependencies

- Check the Timeout

To know more about Timeout configuration of workflows, you can follow this link :

If you cannot resolve your problem, I suggest that you migrate to Power automate and combine many workflows in one Workflow.

Hope that's helpful for you