Best practices for workflow processes


Updated: November 28, 2016

Applies To: Dynamics 365 (online), Dynamics 365 (on-premises), Dynamics CRM 2016, Dynamics CRM Online

This topic contains best practices for creating and managing workflow processes.

It’s possible to create logic in a workflow that initiates an infinite loop, which consumes server resources and affects performance. The typical situation where an infinite loop might occur is if you have a workflow configured to start when an attribute is updated and then updates that attribute in the logic of the workflow. The update action triggers the same workflow that updates the record and triggers the workflow again and again.

Microsoft Dynamics 365 includes logic to detect and stop infinite loops. If a workflow process is run more than a certain number of times on a specific record in a short period of time, the process fails with the following error: This workflow job was canceled because the workflow that started it included an infinite loop. Correct the workflow logic and try again. For Microsoft Dynamics 365 (online) the limit of times is 16. For on-premises deployments of Dynamics 365, the limit is 8.

If you have workflows that are similar and you anticipate creating more workflows that follow the same pattern, save your workflow as a workflow template. This way, the next time you need to create a similar workflow, create the workflow using the template and avoid entering all the conditions and actions from scratch.

In the Create Process dialog, choose New process from an existing template (select from list).

If you apply the same logic in different workflows or in conditional branches, define that logic as a child workflow so you don’t have to replicate that logic manually in each workflow or conditional branch. This helps make your workflows easier to maintain. Instead of examining many workflows that may apply the same logic, you can just update one workflow.

To save disk space, clear the Keep logs for workflow jobs that encounter errors check box if you don’t need to keep this data.

When you edit workflows you should use the Notes tab and type what you did and why you did it. This allows someone else to understand the changes you made.

© 2016 Microsoft. All rights reserved. Copyright

Community Additions