We inadvertently created an infinite workflow loop and for unknown reasons, CRM loop detection did not catch the issue. Does anyone
know how to stop it? We’ve unpublished the workflows to no avail. Other ideas? 4.0 Enviroment Thanks!
Stopping the "Microsoft CRM Asynchronous Processing Service" on the server and then cancelling the jobs, alternatively locating them in the db to stop them, should help.
Stopping the "Microsoft CRM Asynchronous Processing Service" on the server and then cancelling the jobs, alternatively locating them in the db to stop them, should help.