Cisco Bug: CSCuq33198 - Can't override a timed out job after the 2nd run of job
Last Modified
Nov 27, 2020
Products (13)
- Cisco Workload Automation
- Cisco Tidal Enterprise Scheduler 6.2
- Cisco Tidal Enterprise Adapter for VMware
- Cisco Tidal Enterprise Adapter for Oracle E-Business Suite
- Cisco Tidal Enterprise Adapter for Oracle Database
- Cisco Tidal Enterprise Adapter for SAP
- Cisco Tidal Enterprise Adapter for Informatica
- Cisco Tidal Agent for Windows
- Cisco Tidal Enterprise Adapter for Microsoft SQL Server DB
- Cisco Tidal Enterprise Adapter for FTP/SFTP/FTPS

Known Affected Releases
6.2.1
Description (partial)
Symptom: Java Client or Web Browser: Can't override a timed out job after the 2nd run of job Conditions: This is a "continuation" of CSCup92849 . This was fixed in 6.2.1. With that one, you could not override a timed out job in the java client. Now you can. However, if you rerun the job (after the override) and it times out again, you cannot override it the 2nd time. Repro: 1. Create a simple job with a time window. 2. Insert the job into the schedule using the web client after the time window period so that the job will time out. 3. With Java Client or web client, override the job and let it run. 4. With Web client, rerun the job. It should show as timed out. 5. Now with Java client or web client, try to override... Option is grayed out.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Status
- Severity
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases