I have a very simple workflow as seen here:
When a user goes to act on a task, they are presented with an InfoPath form. The form displays some information. The user either selected 'Approve' or 'Reject' from a drop down. When they hit 'Submit', a field called 'approve' in the Tasks extended properties is set. Once approved, the code sets some email properties and other properties based on the selection, sends an email, then completes the task. This all works perfectly and has been tested countless times.
I then needed to deploy an update to the workflow, so I made my code changes, packaged the WSP, and ran an
Update-SPSolution on the workflow. Created a new instance of the workflow (old workflow set to no new instances), and everything works fine. What I'm finding that is those workflows that were created on the original version, if the workflow is sitting at the
OnTaskChanged activity, it does not pickup when a user interacts with the InfoPath form. The associated task is updated, but the on task changed does not seem to fire (as other things are not set/moved forward).
I'm lost on how to troubleshoot this short of running a new instance of the workflow on all of the broken ones.
When creating the new workflow associations, the same Tasks and Workflow History Lists are reused.
Just walked thru the same scenario in my local environment, of not updating a task until a new version of the workflow is out, and I did not have an issue. This seems to be only occurring in the production environment (go figure).