The inline script used for populating a field by flow actions returns the unexpected string "fd-scripted" after you migrate flows with inline script from one instance to another by moving the update setDescriptionUpdate to the field using Inline Script fails when the flow is configured with "Inbound Email" trigger.Steps to Reproduce Instance: New York Patch 4Create a Flow with "Inbound Email" trigger.Add a trigger condition as Subject startswith SNCTESTAdd a "Create Record" action.Select any table like Incident, Change, Problem etcSelect the "Short Description" from the Fields and use the below Inline Script:***var shortDesc1 = '';var shortDesc2 = '';shortDesc1 = fd_data.trigger.subject;shortDesc2 = shortDesc1.replace('SNCTEST', '');return shortDesc2;***Save the flow and Activate.Now, configure any user record with your email id to send an email to the instance.Send an email to the instance with subject "SNCTEST 12345".Expected Behavior: Flow should create a INC record with short description set to "12345" (as we are replacing "SNCTEST' with '').Actual Behavior: Flow creates INC record but fails to update the Short Description field.If we open the Flow context and expand the "Create Record" action, we see "short_description=fd-scripted" in the Configuration and RunTime value.The issue is not happening while doing a test run (runs the flow as System).Workaround Create a custom action containing a script step with the script. Then drag action output to the input field which currently has inline script.Related Problem: PRB1380393