A family of Microsoft on-premises document management and storage systems.
It is resolved after clearing the cache
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Workflow error after migration.
I would say not exactly migration, but it appears to be having some issue. Please refer below response from end user.
Please find user response in the attached screenshots c1,c2 and c3 ( in order)


Please suggest what end user exactly trying to say and what he wants.
however I have compared 2010 and 2016 workflows ( before migration and after migration )
please find attached email body for 2010 workflow and 2016 workflow
highlighted one is missing in 2016, is it causing a problem?

A family of Microsoft on-premises document management and storage systems.
Answer accepted by question author
It is resolved after clearing the cache
Hi @sns ,
As per my understanding, the end user is confused about why variable [%Current Item:ePOD Variation%] in the email body is wrongly displayed. In the screenshot given by the end user, variable [%Current Item:ePOD Variation%] is displayed as DRL008A in email subject but as RPY0014A in email body. So the end user decided to delete [%Current Item:ePOD Variation%] in email body and he found that the workflow to workflow didn't apply his changes. Everything goes on like what is in his first screenshot. In short, the user changed the workflow from the screenshot given by you above(2010) to below(2016), but he found changes didn't been applied.
I would suggest you re-create same workflow and re-publish it to your SharePoint. To see if the new workflow works normally in your end.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.