Customer Engagement & Dynamics CRM Forum

Expand all | Collapse all

Limits in workflows?

  • 1.  Limits in workflows?

    Posted Jul 15, 2019 01:04 PM

    Hello CRM masterminds. :)

    I completed creating a giant workflow to generate notifications based on branch location. We have 26 branch locations in this workflow.... As I begin testing, the first 5 work as expected. As I begin testing the branches beyond that, the workflow never starts (nor shows as failed for that matter) and thus, never emails alerting me that something happened in the branches further along...  Is there a limit to how many things I can have in a workflow?

    Here's a screen shot of the workflow, just imagine it going on for 26 branches since it's the same thing, using the same email template - just branching depending on what building is selected...

    Workflow screen shot showing conditional branches
    Thanks for the insight. :)

    Gretchen Garcia
    IT Technician
    Denver Public Library
    Denver CO

  • 2.  RE: Limits in workflows?

    Posted Jul 16, 2019 02:29 AM
    Hi Gretchen

    There are limits but i don't think you are anywhere near them.

    Have you tried ticking the "on demand" and manually running it against a record.


    Peter Hale
    Naish Pty Ltd


  • 3.  RE: Limits in workflows?

    Posted Jul 16, 2019 02:32 AM
    I'd say the issues are with the trigger.
    The on change field you've selected is somehow not updating.
    Would it make more sense to have the wf trigger on create of the incident?

    Donal McCarthy
    Digital Marketing Administrator


  • 4.  RE: Limits in workflows?

    Posted Jul 16, 2019 07:29 AM
    Hi Gretchen
    regarding your question on limits, there is a limit how many conditions you can have underneith each other. Reaching the limit the system would not allow you to add more. But the way you build your workflow there is no limit.

    If the workflow is not triggered than it is the "Start when" option. Are you sure that the field selected is always changed? What is changing that field? If that is changed from an integration it might might be set to change on the SQL server directly. Or the record is sometimes created.
    If you are not sure what is happening to your record activate Audit Logging on that field and run some tests to see when the field is changed.

    Axel Girgensohn
    Dynamics CRM Specialist
    Aller Media AB


If you've found this thread useful, dive deeper into User Group community content by role