For all Power Tools actions, detailed information is available in the Etere Logs folder (e.g. C:\Users\michael\AppData\Local\Etere\Log\dm.job\), where a file is created for every T-workflow execution. For instance:
mm9.dm.job.27_20141118-123001.a27.j105558.s31c0.d31c0.Powershell.log.psof.xml
<data>
<param name="Result" type="string"><![CDATA[YES]]></param>
<exitCode>0</exitCode>
<error />
<errorExtended><![CDATA[]]></errorExtended>
<log><![CDATA[PsExec version 1.3
Open runspace
Runspace version 2.0
Set SessionStateProxy variables
Create ruspace pipeline
Execute runspace pipeline
Runspace pipeline executed, check output
Get SessionStateProxy variables
output param : name=Result, type=string, value=YES
Close runpace
Error code before writing outfile is 0
]]></log>
<runspace.output><![CDATA[The asset has 3 file(s)]]></runspace.output>
</data>
or
mm9.dm.job._20141118-115943.a52.j105555.s31c0.d31c0.Powershell.log.psof.xml
<data>
<param name="Result" type="string"><![CDATA[NO]]></param>
<exitCode>-4</exitCode>
<error><![CDATA[Script execution failed: The asset doesnt have any files]]></error>
<errorExtended><![CDATA[Script execution failed: The asset doesnt have any files
at System....</errorExtended>
<log><![CDATA[PsExec version 1.3
Open runspace
Runspace version 2.0
Set SessionStateProxy variables
Create ruspace pipeline
Execute runspace pipeline
Get SessionStateProxy variables
output param : name=Output, type=string, value=NO
Close runpace
Error code before writing outfile is -4
]]></log>
<runspace.output><![CDATA[]]></runspace.output>
</data>