In this webinar, our experts showcase a variety of demo use cases of how different components of the...
As you learn about Workflows in Microsoft Dynamics CRM , you may encounter an issue where you find a workflow stuck in "In Progress". You can see an example of this below. Sometimes these workflows might get processed after a long delay.
Today we'll go over how to resolve this issue in an on-premise instance of Microsoft Dynamics CRM. The issue might be related to a missing or wrong value in the MSCRM_CONFIG database.
Select ColumnName, NVarCharColumn
from [MSCRM_CONFIG].[dbo].DeploymentProperties
where ColumnName='ADSdkRootDomain'
or ColumnName='ADWebApplicationRootDomain'
or ColumnName='AsyncSdkRootDomain';
WARNING: Always backup your databases if you are updating data in SQL directly.
If this doesn't resolve your issue, consider opening a request with PowerObjects for support.
Happy CRM'ing!
And also tell your readers what is the consequence of editing CRM database directly. Just in case that somebody doesn't know it.
How do you resolve this on Online version that isn't on-premise?
We have the same issue on CRM 2016, but just from one entity and this help doesn't work for us. is there any other workaround to do this ?
In our case, this just happens only from one entity while calling from plugin and its showing in progress. If we configured to call on create or on update work flow is not hitting. I believe Joe can help up . thank you .