Hi,
In CRM, Workflow is one of the amazing things. If our workflow calls itself (on the same entity) more than 7 times in an hour, the 8th instance will fail with the below error.
"The error is triggered because, by default, CRM only allows for up to eight nested child workflows. When you attempt to run more, CRM will recognize it as an infinite loop and throw error message."
CRM has a limit for this depth. This can seen in MSCRM_Config database by executing the following query.
SELECT * FROM
DEPLOYMENTPROPERTIES
WHERE
COLUMNNAME = 'MessageProcessorMaximumDepth'
If we have really strong requirement that workflow should be called more than 8 times then we can update the value in the Database using the following update query.
WHERE COLUMNNAME = 'MessageProcessorMaximumDepth'
After updating, make sure you reset IIS so that new value will be considered by CRM.
Note: This is unsupported, it may cause issue when you upgrade the CRM system to newer versions.
Hope this helps.
--
Happy CRM'ing
Gopinath
In CRM, Workflow is one of the amazing things. If our workflow calls itself (on the same entity) more than 7 times in an hour, the 8th instance will fail with the below error.
"The error is triggered because, by default, CRM only allows for up to eight nested child workflows. When you attempt to run more, CRM will recognize it as an infinite loop and throw error message."
CRM has a limit for this depth. This can seen in MSCRM_Config database by executing the following query.
SELECT * FROM
DEPLOYMENTPROPERTIES
WHERE
COLUMNNAME = 'MessageProcessorMaximumDepth'
If we have really strong requirement that workflow should be called more than 8 times then we can update the value in the Database using the following update query.
UPDATE DEPLOYMENTPROPERTIES
SET INTCOLUMN = <Number>WHERE COLUMNNAME = 'MessageProcessorMaximumDepth'
After updating, make sure you reset IIS so that new value will be considered by CRM.
Note: This is unsupported, it may cause issue when you upgrade the CRM system to newer versions.
Hope this helps.
--
Happy CRM'ing
Gopinath
No comments:
Post a Comment