Thank you for your answer.
To let you know in advance, I was able to solve it by turning on "use regular expression."
At the time of the question, I was not using regular expressions.
The other options were also as they were when I added the action.
Here is a copy of the action at that time.
SET NewVar TO $'''fi
fi'''
Text.Replace Text: NewVar TextToFind: $'''fi''' IsRegEx: False IgnoreCase: False ReplaceWith: $'''fi''' ActivateEscapeSequences: False Result=> NewVar
SET NewVar2 TO $'''㎍
μg'''
Text.Replace Text: NewVar2 TextToFind: $'''㎍''' IsRegEx: False IgnoreCase: False ReplaceWith: $'''μｇ''' ActivateEscapeSequences: False Result=> NewVar2
I tried to find the problematic symbol using the regular expression you provided, but it didn't work.
So I left the "text to parse" as is and turned on the toggle for "use regular expression" and it worked perfectly.
SET NewVar TO $'''fi
fi'''
Text.Replace Text: NewVar TextToFind: $'''fi''' IsRegEx: True IgnoreCase: False ReplaceWith: $'''fi''' ActivateEscapeSequences: False Result=> NewVar
SET NewVar2 TO $'''㎍
μg'''
Text.Replace Text: NewVar2 TextToFind: $'''㎍''' IsRegEx: True IgnoreCase: False ReplaceWith: $'''μｇ''' ActivateEscapeSequences: False Result=> NewVar2
Actually, there was also a replacement of a string containing "? ", so I didn't use regular expressions.
But, I remembered the existence of an escape text creation action at the same time, so this problem seems to be solved successfully. Thank you.
