Hi @sree_hari
Our team looked into the issue and it comes down to a weird way this specific assign activity was coded in the XAML file. It points to an object while you are assigning a string:
The quick and easy fix here is to:
- remove
str_NewNumber
from the assign activity - save the workflow
- add
str_NewNumber
to the assign activity
This is a workaround.
As to the cause, we are not quite sure how to reproduce the root cause of the wrongly set variable type in the underlying xaml file.
Could you maybe share the steps you took? It would help us properly fix the issue