Laravel Smart Scheduler Laravel Package

Product Decisions This Supports

• Reliability roadmap prioritization: v1.1.0 adds stuck-task detection, making scheduled-job observability a first-class capability. This supports decisions to invest in operational resilience rather than treating scheduler failures as invisible edge cases.
• Build vs. buy: Instead of building custom timeout detection, status tracking, artisan commands, notifications, and model helpers, teams can adopt this package and focus engineering effort on domain-specific workflows.
• Feature scoping for ops/monitoring: The new STATUS_STUCK, isStuck() helper, smart-scheduler:detect-stuck command, and email notifications provide concrete primitives for dashboards, alerting, runbooks, and SLA reporting.
• Incident prevention: Automatic detection before overlap checks helps surface tasks that silently hang, reducing false “all clear” signals and improving mean time to detection.
• Configuration and policy decisions: New stuck_timeout_minutes and notify_on_stuck options let PMs and ops teams define acceptable task durations and notification policies per environment.
• Upgrade planning: The SmartNotifierInterface contract change is a product/engineering coordination point. Any custom notifier implementations must add sendStuckNotification(), which affects upgrade sequencing and release communication.

When to Consider This Package

• Consider it when building or maintaining a Laravel application that relies on scheduled tasks and needs visibility into tasks that exceed expected runtime.
• Strong fit when teams want built-in stuck-task detection, status modeling, artisan-based inspection, and notification hooks without building custom scheduler telemetry.
• Relevant when overlapping scheduled runs are a concern, since the manager now marks stuck tasks before checking overlaps.
• Useful when operations teams need configurable timeout thresholds and optional email alerts for stuck work.
• Look elsewhere if the product needs full workflow orchestration, distributed job scheduling across heterogeneous stacks, or advanced observability already covered by dedicated APM/monitoring platforms.
• Proceed cautiously if custom implementations of SmartNotifierInterface exist, because v1.1.0 introduces a required contract method and should be treated as a coordinated upgrade.

How to Pitch It (Stakeholders)

For executives: v1.1.0 reduces operational risk from silently stuck scheduled tasks. It adds automatic detection, configurable timeout thresholds, status tracking, and email alerts, improving reliability without a custom build.

For engineering: This release adds STATUS_STUCK, isStuck(), smart-scheduler:detect-stuck, stuck_timeout_minutes, and notify_on_stuck. It also changes SmartNotifierInterface by requiring sendStuckNotification(), so custom notifier implementations need an update. The payoff is earlier detection of hung tasks and better overlap safety, with modest upgrade coordination.