Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Workflow went to infinite loop in CRM 2016 On premise

(0) ShareShare
ReportReport
Posted on by

Hi All,

Within an hour,workflow process went to infinite loop after execution of 8th process for that particular record.

So do we need to consider both Parent and Child process for that record if the count exceed 7th process.

Could you please help me out here.

*This post is locked for comments

  • Martin Donnelly Profile Picture
    1,030 on at
    RE: Workflow went to infinite loop in CRM 2016 On premise

    Why would you spawn a process for each value?  Why are you not if...then...else if... 10 times in a single process?

  • Suggested answer
    Dynamics365 Rocker Profile Picture
    7,755 on at
    RE: Workflow went to infinite loop in CRM 2016 On premise

    If you have written any custom code then use context.depth.

    If there is no code then do not run workflow on updated attribute.

    Select only those attributes that are not getting update from workflow.

  • Community Member Profile Picture
    on at
    RE: Workflow went to infinite loop in CRM 2016 On premise

    Hi  Kokulan,

    Thanks for the updates,

    As per the business requirement,based on the update of Optionset workflow will trigger and it has 10 optionset values.

    Could you please confirm me that do we need to consider count of only Parent workflow process or both(Parent-child process) for exceeding 7times in an hours.

  • Suggested answer
    Kokulan Profile Picture
    18,054 on at
    RE: Workflow went to infinite loop in CRM 2016 On premise

    Hi

    In your workflow you have to have a breaking condition or terminating condition.

    Please add Check Condition step and only do the update if the condition is met

    If the condition is not met, the workflow will not update and this will stop it from triggering again and again until the infinite loop exception is thrown.

    One of the best practices is to always have a condition to check the values before you execute the Update step.

    Let us know if you need any further guidance on this.

  • Martin Donnelly Profile Picture
    1,030 on at
    RE: Workflow went to infinite loop in CRM 2016 On premise

    you probably should stop programming infinite loops

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Congratulations to all our community participants!

Adis Hodzic – Community Spotlight

We are honored to recognize Adis Hodzic as our May 2025 Community…

Kudos to the April Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard > Microsoft Dynamics CRM (Archived)

#1
Mohamed Amine Mahmoudi Profile Picture

Mohamed Amine Mahmoudi 83 Super User 2025 Season 1

#2
Community Member Profile Picture

Community Member 52

#3
dkrishna Profile Picture

dkrishna 6

Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans