Thanks, Branfarm. I reviewed the logs in that directory and found three files:
general.log - Hasn't been updated since 2009
scheduller.log - Nothing of interest; A few entries about the process being created and version number
Job-Download Network Device Configs.log - For the last date of the job it shows ~118 entries with the same lines (below). The last entry stops at line:
"6/12/2013 10:44:08 AM - Jobs - --Executing Script"
This may have been where I prematurely stopped the job.
Found that session tracing was already active, so I looked at the latest (by date stamp) file. In fact this was the only file stamped for today's date and no devices (in Node List) have configurations for today, so I wonder if the job got hung on this device? The latest entries were many (tens if not over a hundred) of:
[6/13/2013 7:35:24 AM] TimerTick: mstrData=<> State=3 - Connected to server - idle
[6/13/2013 7:35:26 AM] Pending Disconnect = False
[6/13/2013 7:35:26 AM] Pre-Commands: Waiting more than 3 seconds for response start sending pre-command if any...
[6/13/2013 7:35:26 AM] Fuzzy match detector start detecting prompt. String1= String2=row-b-8810.2#
[6/13/2013 7:35:26 AM] TimerTick: Just tick-tockin away. ..
I'm researching, but is the fuzzy logic looking for a prompt that it's not receiving? These are ExtremeOS switches, where the last character in the prompt changes based on command history.
I manually performed a config download for that device using the right-click menu on the Node List. It completed successfully. My parsing guess may be a red herring, but does the parsing occur differently between a scheduled task and administrator-initiated task? Previous nightly jobs have completed all devices, the just just has not "completed".
In session traces, I went back to the latest-datestamped file for the last date that all configs were downloaded (12 June, yesterday), thinking that perhaps the last device hung. However it appears to have completed successfully, ending with a "Disconnected" log entry.
I am continuing to research and any ideas you have for other areas to explore are greatly appreciated! -Ed