Powershell Step wrong script file path in flow action for custom scriptDescriptionA custom PowerShell script has been added to the Mid server following https://docs.servicenow.com/bundle/vancouver-servicenow-platform/page/product/mid-server/task/mid-server-script-attach.htmlA parent folder was created and the script correctly set to use this folder. eg scriptname = script1.ps1Parent = folder1 The folder and script are correctly synchronised to the MID Server ..\scripts\folder1\script1.ps1 In the Powershell step the the script path is correctly defined \folder1\script1.ps1 On execution the step fails with error IPaasActionProbe | Operation() failed with error: com.snc.process_flow.exception.ProcessAutomationException: The MID script file 'scripts\PowerSHell\\folder1\script1.ps1' doesn't existRelease or EnvironmentAnyCauseThe IPaasActionProbe on the MID server that executes the powershell scripts is hard coded to expect the root folder is PowerShellResolutionEnsure that the Root parent folder for the script is 'PowerShell'In the example above set the Parent of folder1 to PowerShell.Once this has synchronised the script will now have the path: ..\scripts\PowerShell\folder1\script1.ps1 Leave the script path in the PowerShell Step as 'folder1\script1.ps1' With the above the IPaasActionProbe will find the script and the step will run correctly