Powershell activity showing "Exception: The operation completed successfully\n" but results are not as expectedIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms PowerShell activity working in one instance but same PowerShell activity not working in another instance and throwing "Exception: The operation completed successfully\n" Release Istanbul Cause The PowerShell activity commands were triggered as a part of MID Server script file which was not synced on the MID Server end. Thus each time we made changes in test-input, they were never tested as MID Server Script file would just use the old version. Resolution Synced the MID Server script file by restarting the MID Server. Troubleshooting Steps Test the PowerShell activity from the instance where it is working successfully with expected output result.Test the very same PowerShell activity from the instance where it is NOT working successfully and as expected.Change the commands of the activity which is working and note down the outputChange the commands of the activity which is NOT working and compare the output from STEP 3If it does not match it means same activity commands are triggered. Thus the issue is not from the PowerShell activity end.Thus we eliminated one probable cause and now focus on the difference in the process for working case and non-working case (Could be different MID Servers, credentials used, MID Server capabilities, MID Server service account permissions/roles etc..)