Issue:
For the third time in as many weeks, I have had this weird problem in updating the Workflow Settings for one of the SharePoint Lists workflows, whenever I change the Start Options to “Start workflow automatically when an item is created/changed” and publish it to SharePoint, the start behavior of the WF execution doesn’t change and once I refresh the SharePoint Designer (SPD) and check the start options again, it returns as it was “Allow this workflow to be manually started”.
Cause:
After many hours of fighting with SPD, I went to a conclusion that SPD will cause this issue sometimes because of certain Workflow Activities .NET assemblies caching problem within the SPD.
Resolution:
The solution? It’s simple, you have to clear the SPD Workflow Activities Assembly Cache Folders:
-
Close the SharePoint Designer.
-
Delete all these directories inside the ProxyAssemblyCache Folder.
-
Delete all the files inside this Folder.
-
Run SPD again, and everything will work out fine
[…] This post was mentioned on Twitter by Mohamed Saleh, SP2010CL(PL). SP2010CL(PL) said: https://maspoint.wordpress.com/2011/01/25/sharepoint-designer-2010-workflow-updating-issue/ […]
Thanks for the fix. you saved me a lot of time
hey thanks man!
This saved me some headache..
Thanks for the fix
you saved me a lot of trouble, thanks.
really useful tip,thanks.
Hi Friend,
I been facing the exact same problem with SPD2010 in SPS2010. WF’s were working fine until today morning, but suddenly it stopped updating, so whenever I publish(new WFs) or re-publish(old WFs) it doesn’t seems to be updating, as it is performing the same old steps(for old WF’s). Files in ProxyAssemblyCache folder were updated around 4 hours back. Performed the steps mentioned above and was successful for the first time but soon after faced the same problem and again performed the above steps but the problem isn’t resolved. Please comment on this.
Regards,
Sravan.
——————————————————————————–
sorry for this delay in replying, but did you remove the old workflow instances from the workflow history?
Thank you for returning back, yes I did removed all the old instances of WF before performing the operation.
So If it’s not working right now, I assume that you are using an administrator account to run the WF?