So, the whole process of the way loops are handled still confuses me. For example, we have a job that has this structure:

* Get computer names from an AD group
[begin loop using for each x in {TASK(7b2cde0d-d66d-4416-9bbd-e7306764f5f3,StdOut)}]
* Set a user variable to {LOOP(CurrentValueX)}
* Restart the computer using the user variable
[end loop]

When we get errors like the one below, how do we figure out what value (computer name) was being using in this task when it failed? It's working for all of them some of the time and most of the them all of the time. Only once in a while is it failing on what seems like one computer.

"Exception in Task: Error occured:The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)"

It would be nice if the failure output would contain the value used, like you mentioned. An alternative method (not desired) would be to generate a notification immediately using the variable for the loop somewhere in the text upon task failure. That way you'd have the value 'somewhere'.

Brian

I agree.

This is what we came up with it to add to the task error email notification:
Loop Value: {USERVAR(CURRENT_LOOP_VALUE)}

I am moving this to Feature request and the change will be that we add the Computer name (that is currently used) to the error output.

---

I'm not sure if you are understanding the request. Are you speaking specifically about a restart task? If so, that is just an example. We have this issue anytime we use loops - not know where the loop was at the time of failure.

I see. A little more complex then as that value is not available when in the Notification but then we know what you want. Thanks.

---