afaik it's normal behaviour if the server is a target of the job when it was decomissioned. it's not actually running against it, i think it's just a placeholder like "i would have run against this server but you decomissioned it"
what really is missing is a "show dependency" menu option for servers like there is for depot objects, so we can check before decommissioning a server, where it is used
Thanks for that Bill.
But... The job was created AFTER the server had been decommissioned. However, the server had, previously, been a member of the SmartGroup that was being used as the "target". Could there have been a delay in the server's removal from the SmartGroup?
i'm not sure if this is possible - how much longer after the decomission was the job created?
as soon as the server is decomissioned it will be removed from the gui and the smart group. it should only take a few seconds for the decomission to complete, maybe a minute at the most.
usually i only see this if the server is the direct target of a job and you de-comm the server. it stays as a target of the job but it's greyed out.