Description:

Currently, a single system job that becomes stuck or fails can block all subsequent jobs of the same type until an administrator manually intervenes. This creates operational risk and delays, especially in environments where these jobs are critical to ongoing processes.

There are two key gaps that would benefit from enhancement:

1. Automatic Recovery / Retry Logic

• The platform should provide smarter, configurable retry behavior.
• Future jobs of the same type should be able to continue when one job becomes stuck, or the system should automatically skip or cancel the problematic job after a defined threshold.

1. Out‑of‑the‑Box Alerting

• There is no native alerting when a system job fails, stalls, or blocks a queue.
• Administrators must build custom monitoring to detect these issues.
• Built‑in notifications (email, dashboard alerts) would significantly reduce downtime and manual oversight.

Value / Impact

Enhancing resiliency and adding native alerting would:

• Prevent entire job pipelines from being blocked
• Reduce the need for manual monitoring and intervention
• Improve system reliability and transparency
• Lower operational overhead for administrators

Requested Features

• Configurable auto‑retry and auto‑skip behavior for system jobs
• Automatic detection of “stuck” jobs
• Native alerting when a job fails or blocks subsequent jobs
• Optional escalation rules (e.g., notify after X minutes or X failures)