Workflow caught in a loop. Dynamics 365

(0) Share

Report

Posted on by Community Member

I created a simple workflow yesterday to update a field when the sales process moved to the next stage. However i didn't put an end to the workflow and it now seems to be caught in a infinity loop running a couple of times a minutes and it won't stop. I have tried the following to little success.

Deactivated all the workflows
Deleted the workflows
Attempted to delete the associated opportunity that the workflow was linked to. Get SQL server error now think due to the workflows taking up all resources.
Went to system jobs (now 5000+) and have tried cancelling all system jobs but it just keeps reoccurring.
Attempted to do a bulk delete on the Opportunities associated to the workflow, and the system jobs but status is that it is waiting for resources.

I have read about turning off the asynchronous service but i am unable to find anywhere to do this in Dynamics 365. I'm starting to run out of idea and any help would be very much appreciated before i give up and move to Salesforce!!!

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Tommy Lauritzen 350 on at

Like (0)

Report

What event is this workflow triggered on? sounds like you have alot of creates/updates being done in the system and you've managed to generate a massive backlog of workflows queued for execution.

if you have deactivated the workflow as you say, you will not see new sessions being triggered, and it will eventually stop running new ones.

if this is not the case, I would create a support ticket for the issue as you do not have access to the server or database.

If you are on premises, then you will find the asynchronous service (name MSCRMAsyncService) running on the backend server. Stopping this shuts off processing.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Tommy,

I will raise a call with Microsoft as after leaving it over the weekend its still going.

Confusing thing is that the workflow has been deactivated and deleted from the system. Yet according to the system jobs element the job are still being created a few times a minute. I've raised a call with Microsoft as you have suggested so fingers crossed once they have killed it off it won't start back up again when they turn the service back on.

Thanks,

Tom

Was this reply helpful? Yes No
Zibba360 on at

Like (0)

Report

Hi TOMudd

How is the setup of the workflow and is it only OOB or has custom workflow activity. Does it only trigger on field change? Can you post pictures or code?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Its just out the box and very simple. I set it to run before the process ID changed and it was to update a single field with a new value. I would post pictures of the code used to set it up but as part of me attempting to fix the issue I deleted the workflow and so don't have access to code any more.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello, TOMudd,

we have the same problem!

Have you found a solution?

Was this reply helpful? Yes No

Community site session details

Workflow caught in a loop. Dynamics 365

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Featured topics

Product updates

Community site session details

Workflow caught in a loop. Dynamics 365

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Featured topics

Product updates