SCH Job Monitoring / Job History should display the lastest SDC ID(s) on which a failover retry was attempted

When an SCH job fails over and enters INACTIVE_RED, there is currently no way for end users to tell via the Job Monitoring UI or Job History UI which SDC ID(s) the job is currently attempting to be retried on if the job is failing due to a START_ERROR.

• The customer had an issues where many jobs were stuck in ACTIVE_RED after failing over and had exceeded their Per Data Collector retry limits.
  • Their SDC VM's periodically get recreated during maintenance, and their SDC's are deleted and re-created with new SDC ID's but the same SDC hostname as before.
  • The problem was when their jobs failover after mainatainance, the SCH UI gave unclear information about what engines their jobs were trying to failover to:
• Job Monitoring UI:
  • The bottom right of the Job Summary does not reflect the latest SDC engine ID the job was attempted to start on-- it seems to only update if the job passes validation and enters RUNNING on the new SDC.
  • The customer's jobs had START_ERROR's when failing over to the new SDC, which meant the UI continued displaying the SDC ID of the old (and deleted) SDC, and did not show a failover was attempted on the new SDC engine.
  • Because the engine ID doesn't update in Job Monitoring UI, even clicking the SDC Logs Icon links to the old engine's logs (which no longer exist because the engine is deleted) and not the latest engine showing what the START_ERROR was.
• Job History
  • The Job History logs the failover attempts, but it only logs the SDC hostname, not the SDC ID.
  • This is ambiguous when engines are deleted/created with the same SDC hostname since it's unclear what engine ID the failover was attempted on:

Failing over job from Data Collector 'https://dc1.example.com:18630' to Data Collector
"https://dc1.example.com:18630'. retry count is'1'

Ideally, the Jobs UI should be able to reflect to the end user the latest SDC engine info so even if a job has START_ERROR's during failover, it is clear which engine the START_ERROR occurred on and which engine(s) failovers were attempted.