1) Problem Description :

-> Currently, under the "Jobs" section in the system settings, we can set global values for Default Job Idle Timeout and Default Job Running Timeout. However, we would like to request an enhancement to allow these timeout settings to be defined per container group.

This would provide greater flexibility in managing jobs with different runtime expectations. 

Example use cases:

Container Group: "Incident-Jobs"
These jobs are designed to run for extended durations, such as disk cleanup tasks.

Running Timeout: 8 hours
Idle Timeout: 8 hours

Container Group: "AAP-Jobs"
These jobs are expected to complete more quickly.

Running Timeout: 4 hours
Idle Timeout: 1 hour

2) Business Impact :

-> Introducing per-instance (container group) job timeout configurations would significantly enhance operational efficiency and resource management.

-> This level of granularity would give better control and flexibility over job execution based on their purpose and expected behavior.