We commonly observe repeating fields in emails. We originally thought it happened when we use a reference to start a loop in the workflow, and the documentation supports this. However I came across one today that is not in a loop.
An example might look like this. The field provides the value "None":
Management Engagment Required: NoneNoneNoneNoneNone
The workflow is fairly simple, but muliple paths call the same subworkflow, and those paths are all from a shared split step. The split step splits into multiple paths and those paths all call the identical subworkflow, but with different input parameters. I'm not sure if that matters to the issue. The fields with the issue are all from a reference. We're seeing this now that we have multiple users on the system at the same time. It appears as if K2 has a concurrency bug with references.
I'd like some insight into fixing this. I removed the references and now I make a SMO call and use regular workflow variables. This is a scary one for us becuase we use references all over the place and we've only started concurrent user testing right now.
