web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

🚀 Season of Sharing Community Challenge Launch! 🚀
Ask A Community Pro
Introducing our New Video Series: Community Spotlight
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Workflow went to infin...
Microsoft Dynamics CRM (Archived)

Workflow went to infinite loop in CRM 2016 On premise

(0) ShareShare
ReportReport
Posted on by Community Member

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

I have the same question (0)
  • Martin Donnelly Profile Picture
    Martin Donnelly 1,030 on at

    you probably should stop programming infinite loops

  • Suggested answer
    Kokulan Profile Picture
    Kokulan 18,054 on at

    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.

  • Community Member Profile Picture
    Community Member on at

    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
    Dynamics365 Rocker Profile Picture
    Dynamics365 Rocker 7,755 on at

    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.

  • Martin Donnelly Profile Picture
    Martin Donnelly 1,030 on at

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

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

News and Announcements

🚀 Season of Sharing Community Challenge Launch! 🚀
Ask A Community Pro
Introducing our New Video Series: Community Spotlight

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
ScottDurow Profile Picture

ScottDurow 2

#2
GJones Profile Picture

GJones 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans