Symptoms

I added a Process Association to my Workflow in K2 Studio, but there was an issue with the mappings to the SMO so I removed all association details from the Process. However, it is clear some of the changes that were created when making this association were not rolled back when I removed the association because now I cannot deploy my Workflow due to an error with the SMO that I had associated, but removed.
 

Diagnoses

The workflow deployed correctly the first time we tried it on the Go To Meeting.
 

Resolution

We discussed that sometimes a workflow may deploy after a few tries because it did not write the back-end code correctly or completely on the first tries. This is most likely to happen when a previously deployed workflow gets modified.