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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

System Jobs running Twice since 2013 upgrade

(0) ShareShare
ReportReport
Posted on by 895

Since we were upgraded to Dynamics CRM 2013 a background workflow seems to be running twice.

The workflow used to run when Mark Complete was tagged and it looked at a field on the form and raised a different action based on what was selected, now every time 1 of the users marks a call as complete we instead get two calls created. I am guessing this is related to when a call is saved but is there a way to ensure each workflow is only run once?

Thanks

*This post is locked for comments

I have the same question (0)
  • AdamBrown55 Profile Picture
    895 on at

    Hi, Bit more info, It appears that when clicking on Mark Complete it is first changing the status to Scheduled and then Changing it again to Complete - I guess this is why it is running the workflow twice.

    The first line of the process says to just run on completed so I am guessing it is picking up the completed status from the second change when it runs the first.

    Any help would be appreciated as obviously we are starting to get lots of extra appointments raised.

  • Community Member Profile Picture
    on at

    Hi Adam.

    We just started having the exact same issue. We have moved our organization from CRM 2011 to CRM 2013 On Premise.

    The problem to us is happening with all workflows and is happening very randomly and casually. There is no pattern.

    Can you tell me if you were able to solve the problem, or someone else can provide us with a solution to this?

    This is creating appointments twice for us and it's a big issue because this way we never have correct statistics and reports!!!!

    Anyone that can help about this ASAP?

    Thank you

  • AdamBrown55 Profile Picture
    895 on at

    Hi, we did kind of get it sorted. The problem was that it was running in the background this caused it to run on both status updates. I changed the workflow to run real time and then it still ran twice on both status changes but only the second one raised a call. Not a great solution but solved the problem.

    Hope it helps.

  • Community Member Profile Picture
    on at

    Thanks Adam,

    We converted some of them too but some others can't be converted in real time. I hope Microsoft provides us with a definitive solution for this.

  • Community Member Profile Picture
    on at

    Hi again Adam,

    I have an update about this. I tested something by myself and now I am also talking with Microsoft support about this issue.

    If I disable the problematic workflows and recreate them, it seems to be working fine. This might have been an issue during the import from CRM 2011 to CRM 2013, so you can try the following steps to solve this problem :

    1. Disable problematic workflow.

    2. Create new workflow.

    3. Reproduce inside the new workflow, all the steps of the old problematic workflow.

    4. Enable the new workflow.

    We are testing from a while and I can't yet provide you a definitive solution but I can tell you that we have other workflows that are still being executed multiple times but the new one is working fine.

    I am also trying to solve this problem with Microsoft support and find the real reason behind this, but in the meantime, this seems like a solution for us.

    Also something that I forgot to mention. Strangely enough, for us this is happening randomly and it's happening only for the workflows that are related to the LEAD entity.

    Regards,

    Ermal

  • Community Member Profile Picture
    on at

    Hi Adam,

    Just wanted to update you that the problem happened with the new workflows too. I will update again with the reply from Microsoft.

    Ermal

  • ChFarr Profile Picture
    5 on at

    Hi Ermal,

    Did you manage to get a response from Microsoft on this?

    Thanks

    Charmaine

  • Suggested answer
    Community Member Profile Picture
    on at

    Hi Charmaine,

    This was a bug with the "SAVE" javascript that the CRM uses and with CRM Outlook 2013 Client. When we tried this from the Outlook 2011 client, the bug didn't happen, but it still duplicated the records when trying from the browser.

    This issue has been resolved with Update Rollup 2 for CRM 2013. Apply the update that you find here :

    support.microsoft.com/.../2919956

    in your server and clients and you will find the "Save & Close" button that was there before in CRM 2011 and I have no idea why Microsoft removed it from CRM 2013, because it was very useful to us. Finally it's back now.

    I hope this helps you.

    Regards,

    Ermal

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans