Sentry reports invalid schedule for schedules that should be valid
Open
Nobody has claimed this yet.
Bug
Crons
Product Area: Crons
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
- Edit existing cron monitor with schedule of type "Interval" set to "Every 5 minutes".
- Change to "Every 6 minutes".
- Click on "Save" button.
- Sentry reports "Invalid schedule for schedule unit count".
Note that it also reported this when I tried other values I expected to be valid, like 1 or 10.
Expected Result
Saves the cron monitor with the new valid value.
Actual Result
Product Area
Crons
Link
No response
DSN
No response
Version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the interval cron monitor flow in the Sentry SaaS environment, changing an existing schedule from every 5 minutes to values such as 1, 6, or 10. Trace where the “Invalid schedule for schedule unit count” validation is produced and add regression coverage for valid interval values. Done means valid values save successfully without the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 63/100