SharePoint 2013 workflow deployment doens't update workflow definition - by Sohel Rana

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 779905 Comments
Status Closed Workarounds
Type Bug Repros 13
Opened 2/24/2013 6:39:56 PM
Access Restriction Public


In Visual Studio 2012, we can develop SharePoint 2013 workflow and deploy directly in SharePoint. However, once a workflow is deployed and later modified and redeployed, the modified workflow definition doesn't take effects. Even if you retract the solution and redeploy, the associated workflow with the sharepoint solution doesn't get updated in the SharePoint. Retracting the SharePoint solution then restarting the development server and finally redeploying will reset the workflow definition. 
Sign in to post a comment.
Posted by Alfonso Clemente on 10/29/2014 at 3:24 AM
Those workarounds didn't work for me.
Posted by Steven-Hughes on 9/9/2014 at 12:44 PM
Still no solution? Is there an ETA?
Posted by papadi on 1/13/2014 at 7:41 AM
Nothing yet?
Posted by Microsoft on 8/13/2013 at 3:34 PM
We are currently with with the Office team to fix this issue. Thank you for your patience.
Posted by bwodicka on 4/9/2013 at 12:07 PM
Has there been any answer on this? I have also been experiencing this problem -- seems like the old workflow definition is being cached somewhere and not refreshed on deployment from VS. Any direction would be greatly appreciated!
Posted by Sohel Rana on 3/25/2013 at 1:09 AM

I can still reproduce the issue with most recent builds. Even after deploying the Workflow, I have restarted the IIS and workflow service but still the old workflow runs inside SharePoint. My VS 2012 version is 11.0.50727.1 RTMREL

I've attached a Visual Studio project ( to reproduce the scenario. In the attached project, there's a workflow. In that workflow, the activity SetField has a property 'FieldValue' whose value is 'Message 1'. When you first deploy the workflow and associate with a document library and then execute it against a document, you will find the document title has been changed to 'Message 1'. Then if you change the message to 'Message 2' in Visual studio and redeploy/execute the workflow, you will find the workflow still writing 'Message 1' in the title. Resetting IIS and workflow service doesn't help. Developers need to change in workflow very often during development and if there's no workaround to this problem, then it'll hamper productivity.
Posted by Microsoft on 3/19/2013 at 2:18 PM
This issue could not be reproduced with our more recent builds. Please use the official release of Office Developer Tools for Visual Studio 2012. Download from:
Posted by zemlvp on 3/5/2013 at 10:21 AM
In my opinion this problem is happens in farm solution only
Posted by Microsoft on 2/25/2013 at 6:38 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 2/24/2013 at 6:52 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(