Skip to content

Fix: Detect and warn when schedules generate multiple CRONs #707

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
himanshukale36 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix: Detect and warn when schedules generate multiple CRONs #707

himanshukale36 wants to merge 1 commit into from
+32 −2

Conversation

@himanshukale36
Copy link

@himanshukale36 himanshukale36 commented Jan 15, 2026

Fixes #703

  • Use Fugit::Nat.parse with multi: :fail to detect schedules that generate multiple CRONs
  • Raise validation error with clear message when multiple CRONs detected
  • Add tests for single CRON, multiple times (same/different minutes)
  • Prevents silent failures where only first CRON was used

@himanshukale36
Fix: Detect and warn when schedules generate multiple CRONs
d23e354 
Fixes rails#703

- Use Fugit::Nat.parse with multi: :fail to detect schedules that generate multiple CRONs
- Raise validation error with clear message when multiple CRONs detected
- Add tests for single CRON, multiple times (same/different minutes)
- Prevents silent failures where only first CRON was used
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

solid_queue doesn't raise a warning when fugit should generate multiple CRONs

1 participant

@himanshukale36