Workflow hangs with Status Reason: Waiting for Resources

Question Status

Suggested Answer
Marius Mihalca asked a question on 29 May 2015 3:58 AM

I am trying to build some workflows, but regardless of its complexity the workflow hangs with Status Reason: Waiting for Resources. Tried already to restart CRM services. Anyone has an ideea on how to fix this behavior?

Reply
Rajkumar Rajaraman responded on 29 May 2015 4:05 AM

Hi Marius,

Restart your ASYNC services.

The asynchronous services are on the CRM server, in the control panel - services.

service name

MSCRMAsyncService

Display name

Microsoft Dynamics CRM Asynchronous Processing Service

Sometimes the Asynchronous service can get stuck or consume lots of memory and then become very slow.

Hope this helps.

Regards,

R.Rajkumar

"Please mark my answer as verified if you found it helpful"

Reply
Suggested Answer
Rajkumar Rajaraman responded on 29 May 2015 4:08 AM

Hi Marius,

Refer this link also:

blogs.msdn.com/.../dynamics-crm-troubleshooting-workflows.aspx

Hope this helps.

Regards,

R.Rajkumra

Reply
Marius Mihalca responded on 12 Jun 2015 2:15 AM

I did that and and it did not affect the workflow's status.

Reply
Priyadarshi Purwar responded on 12 Jun 2015 2:28 AM

It is  waiting for all records or only with some/particular record.

Reply
Suggested Answer
Priyadarshi Purwar responded on 12 Jun 2015 2:30 AM

You can check details of Workflow (top left side).

Reply
Nuno Almeida responded on 13 Jun 2015 5:11 AM

Hi Marius,

What is your workflow doing?

Reply
Marius Mihalca responded on 15 Jun 2015 6:32 AM

So far I’ve discovered that Real-Time Workflows are working. Once i convert it to background workflow it's not working anymore (it is not called by the system).

So, this raises a question. I need to send 1 email notification once I activate a contract and I need to send 3 notifications before the contract expires. I plan to do 2 workflows: Activation Notification and Expiring Notification (90 days, 60 days, 30 days). These workflows should be Real-Time Workflows or Run in Background Workflows? What is recommended?

Reply
Suggested Answer
Priyadarshi Purwar responded on 16 Jun 2015 6:17 AM

It should be background workflow.

1-Background workflows are generally recommended because:

2-They allow the system to apply them as resources on the server are available

3-Help maintain the best performance for everyone using the system

4-They are fine for most automation of business processes because the people using the system don’t need to be consciously aware that the process is running.

Use real-time workflow:

1-When a business process requires someone to immediately see the results of the process

For example, you want to set certain default values for a record the first time it is saved

Or you want to make sure that some records are not deleted

2-If you want the abilityto cancel an operation

Reply
Andre Krijnen responded on 16 Jun 2016 4:42 AM

Hi,

When you have the message waiting for resources it tries to process all tasks and workflows. I don't know your environment looks like, but you can try to tweak the table "DeploymentProperties" in the MSCRM_Config table.

Update the fields:

AsyncItemsInMemoryHigh from the current value (most likely 20) to for example 200

AsyncItemsInMemoryLow from the current value (most likely 10) to for example 100

It enables the AsyncService to process more items in memory.

Reply
Ganesh Naral responded on 14 Jul 2016 10:48 AM

please do explain how to do that, facing same problem

Reply
AlejandroRTovar responded on 11 Nov 2016 12:11 PM

Hi Marius, you have any update about it ?. I have the same problem, the only difference I using a workflow custom activity attach to workflow, is run perfect on sync mode, but hangs "Waiting for resources" in async

Reply
Suggested Answer
Rajkumar Rajaraman responded on 29 May 2015 4:08 AM

Hi Marius,

Refer this link also:

blogs.msdn.com/.../dynamics-crm-troubleshooting-workflows.aspx

Hope this helps.

Regards,

R.Rajkumra

Reply
Suggested Answer
Priyadarshi Purwar responded on 12 Jun 2015 2:30 AM

You can check details of Workflow (top left side).

Reply
Suggested Answer
Priyadarshi Purwar responded on 16 Jun 2015 6:17 AM

It should be background workflow.

1-Background workflows are generally recommended because:

2-They allow the system to apply them as resources on the server are available

3-Help maintain the best performance for everyone using the system

4-They are fine for most automation of business processes because the people using the system don’t need to be consciously aware that the process is running.

Use real-time workflow:

1-When a business process requires someone to immediately see the results of the process

For example, you want to set certain default values for a record the first time it is saved

Or you want to make sure that some records are not deleted

2-If you want the abilityto cancel an operation

Reply