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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

what causes a workflow to fire too often?

(0) ShareShare
ReportReport
Posted on by

Nothing fancy.  It is supposed to fire on status change of an order (onSubmit) and it fires 2 or more times.

SubmitOrder.PNG all the update does is set Date Submitted to the session execution time.

If I did this in a plugin, I wouldn't expect there to be multiple status change events.  Why should there be many here?

Setting the date should not be a status change.  Other threads speak of infinite loops.  Status change should not act infinitely.

I've seen this on other workflows that are just too simple to be a developer issue, e.g. the assign template step to generate a quote pdf.

I have the same question (0)
  • Suggested answer
    Adrian Begovich Profile Picture
    1,027 Moderator on at

    Hi TallyHoDukey,

    The workflow starts whenever the status of an Order changes regardless of the status it changes to. It is only once the workflow starts that it checks whether or not the status equals submitted. This could lead to the workflow firing more often than expected. I recommend unchecking the Automatically delete completed workflow jobs (to save disk space) option, performing the actions that cause the workflow to execute, and examining the workflow job to determine what is happening.

  • Community Member Profile Picture
    on at

    Yes, but I'm not talking about over time.

    This workflow is firing multiple times within the same minute for the same status change event.

  • Suggested answer
    Adrian Begovich Profile Picture
    1,027 Moderator on at

    Hi TallyHoDukey,

    You need to enable the Automatically delete completed workflow jobs (to save disk space) option to be absolutely sure that the same workflow is executing multiple times within the same minute. It is possible that another workflow or plugin is running on the Order entity in parallel.

  • rthompson Profile Picture
    1,532 on at

    Hi,

    Can you duplicate the same issue in your development account.

    If so,  I would do the following.

    This is base on me not knowing what your order entity is doing.

    I would turn on the Trace log.

    My first check review your javascript onSave event to see what that is doing.

    Then I would check my plugins if any.

    Then I would disable the workflow and enable the workflow.

    I am sure 1 of the 3 is causing your issue.

  • Community Member Profile Picture
    on at

    I wouldn't lie to you

    noLie.PNG

  • Community Member Profile Picture
    on at

    ps- I'm getting these even though the auto delete is activated.  Could this be some sort of phantom system job creation?

  • Fubar Profile Picture
    2,761 on at

    Turn on the audit history and see if there are updates / status changes happening or if there is just 1 entry.

    Possibly try unchecking status change and change it to trigger on Status Reason change and see what happens.  Can also try switching it to real-time to see what happens.

  • rthompson Profile Picture
    1,532 on at

    Hi,

    Can you duplicate the same issue in your development account.

    If so,  I would do the following.

    This is base on me not knowing what your order entity is doing.

    I would turn on the Trace log.

    My first check review your javascript onSave event to see what that is doing.

    Then I would check my plugins if any.

    Then I would disable the workflow and enable the workflow.

    I am sure 1 of the 3 is causing your issue.

  • LeoAlt Profile Picture
    16,331 Moderator on at

    Hi partner,

    I created a new workflow with the same steps of yours and when I change the status to Submitted, this workflow only ran one time.

    pastedimage1580349448085v1.png

    So there should be some other processes or plug-ins or other possibilities which may cause this situation. Please do the following check.

    1.Enable the field audit of status and monitor this field for several changes when trigger the workflow.

    2.Check if there is any other processes or plug-in work with order.

    Best Regards,

    Leo

  • Suggested answer
    Charles Abi Khirs Profile Picture
    3,569 on at

    Hello,

    Since there are no Plugins/WFs/JS involved with this action, I suggest to open a ticket with Microsoft support in order to resolve this issue as it might be a bug in the product.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 70 Super User 2025 Season 2

#2
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 33 Most Valuable Professional

#3
Daniyal Khaleel Profile Picture

Daniyal Khaleel 32 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans