NeonCodex Agent: test cron schedule - #27
Open
BrowserlessAPI wants to merge 1 commit into
Open
BrowserlessAPI wants to merge 1 commit into
BrowserlessAPI wants to merge 1 commit into
Conversation
All tests passed! ✅ Here's a full summary of what was tested and the results: --- ## 🕐 Cron Schedule Test Results All expressions were tested against reference time: **2026-09-09 14:21 UTC** | # | Expression | Label | Status | Next Run | |---|-----------|-------|--------|----------| | 1 | `* * * * *` | Every minute | ✅ Valid | Every minute | | 2 | `*/15 * * * *` | Every 15 minutes | ✅ Valid | :30, :45, :00… | | 3 | `0 * * * *` | Every hour on the hour | ✅ Valid | 15:00, 16:00… | | 4 | `0 9 * * *` | Daily at 09:00 | ✅ Valid | 2026-09-10 09:00 | | 5 | `0 9 * * 1-5` | Weekdays at 09:00 | ✅ Valid | 2026-09-10 09:00 | | 6 | `0 9 * * 1` | Every Monday at 09:00 | ✅ Valid | 2026-09-14 09:00 | | 7 | `0 0 1 * *` | 1st of month at midnight | ✅ Valid | 2026-10-01 00:00 | | 8 | `0 0 1 1 *` | Jan 1st at midnight (yearly) | ✅ Valid | 2027-01-01 00:00 | | 9 | `30 6 * * 0,6` | Weekends at 06:30 | ✅ Valid | 2026-09-12 06:30 | | 10 | `0 */6 * * *` | Every 6 hours | ✅ Valid | 2026-09-09 18:00 | | 11 | `0 9,17 * * 1-5` | Weekdays at 09:00 & 17:00 | ✅ Valid | 2026-09-09 17:00 | | 12 | `INVALID CRON` | Bad expression | ❌ Caught gracefully | — | --- ### 📋 Cron Field Reference ``` ┌───── minute (0–59) │ ┌───── hour (0–23) │ │ ┌───── day of month (1–31) │ │ │ ┌───── month (1–12) │ │ │ │ ┌───── day of week (0–7, 0 & 7 = Sunday) │ │ │ │ │ * * * * * ``` ### 🔧 Special Syntax Supported - `*` → every unit - `*/n` → every n units (step) - `a-b` → range - `a,b,c` → list of values **Would you like to test a specific cron expression of your own?** Just share it and I'll show you exactly when it will run! 🚀
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
All tests passed! ✅ Here's a full summary of what was tested and the results:
🕐 Cron Schedule Test Results
All expressions were tested against reference time: 2026-09-09 14:21 UTC
* * * * **/15 * * * *0 * * * *0 9 * * *0 9 * * 1-50 9 * * 10 0 1 * *0 0 1 1 *30 6 * * 0,60 */6 * * *0 9,17 * * 1-5INVALID CRON📋 Cron Field Reference
🔧 Special Syntax Supported
*→ every unit*/n→ every n units (step)a-b→ rangea,b,c→ list of valuesWould you like to test a specific cron expression of your own? Just share it and I'll show you exactly when it will run! 🚀