The customer didn't have time for me to get all the information needed to escalate a case right now, so I thought I'd start this here. 

customer has a particular workflow whose first activity is pulling about 25 fields from a document with a retrieve activity. The document he is pulling from is mostly empty at this point, there's only about 2-3 fields on the template that are actually retrieved when we look at the tokens generated by the activity. Instead of populating the actual template name, it is taking the value of one of the fields that it's retrieving and presenting that as the template name in subsequent activities. Unfortunately this is a very large, complex workflow so simply blowing it away and putting it back on will cause a very large amount of work because of a huge number of conditionals in multiple trees below. 

Everything in this workflow hinges on getting the correct template back, and this workflow has been working correctly for quite a while. Has anyone seen this before? Is the only solution to roll back to a previous version of the workflow? It hasn't been published for a while before the issue started happening. 

He is on the latest version of the 9.2 release.