input stringlengths 9 17 | label stringlengths 12 46 | note stringlengths 66 115 |
|---|---|---|
* * * * * | Every minute | The most frequent possible schedule, often used for monitoring or very high-frequency tasks. |
0 * * * * | Every hour on the hour | Common for hourly reports, data synchronization, or health checks. |
0 0 * * * | Every day at midnight | Ideal for daily backups, data processing, or generating daily reports. |
*/5 * * * * | Every 5 minutes | Useful for frequent polling, cache refreshing, or near real-time updates. |
*/15 * * * * | Every 15 minutes | Good for tasks requiring regular but not constant updates, like checking queues or processing small batches. |
*/30 * * * * | Every 30 minutes | Suitable for tasks that need to run twice an hour, like status updates or partial data synchronization. |
30 * * * * | Every hour at 30 minutes past the hour | Allows for staggered hourly tasks or offset from the top of the hour to avoid peak load. |
0 */6 * * * | Every 6 hours | For less frequent but regular checks, like system health monitoring or data aggregation. |
0 */12 * * * | Every 12 hours | Common for tasks that need to run twice a day, such as daily summaries or large data refreshes. |
0 9 * * 1-5 | Every weekday at 9 AM | Ideal for business-hour specific tasks, like morning reports or system readiness checks. |
0 0 * * 6,0 | Every weekend at midnight | For weekend-specific maintenance, data processing, or reporting tasks. |
0 8 * * 1 | Every Monday at 8 AM | Useful for weekly reports, system cleanups, or start-of-week preparations. |
0 0 1 * * | First day of every month at midnight | Common for monthly billing, archiving, or generating monthly summaries. |
0 3 * * 0 | Every Sunday at 3 AM | Often used for weekly deep maintenance, backups, or system reboots during low usage times. |
0 9 * * * | Every day at 9 AM | For tasks that need to run at the start of the business day, like sending daily digests. |
0 17 * * * | Every day at 5 PM | Suitable for end-of-day processes, like sending summaries or preparing for overnight jobs. |
0 */2 * * * | Every 2 hours | For tasks requiring more frequent than daily, but less frequent than hourly execution. |
0 1,13 * * * | Every day at 1 AM and 1 PM | For tasks that need to run twice a day at specific, non-offset times. |
0 0 1 1,4,7,10 * | First day of every quarter at midnight | For quarterly reporting, financial statements, or long-term data archiving. |
0 10 * * 2 | Every Tuesday at 10 AM | For specific weekly tasks scheduled on a particular day of the week, like a weekly report or sync. |
*/10 * * * * | Every 10 minutes | A common interval for monitoring or tasks that require regular updates without being too aggressive. |
30 2 * * * | Every day at 2:30 AM | Good for tasks that need to run in the early morning hours, typically when system load is low. |
0 10,16 * * 1-5 | Every weekday at 10 AM and 4 PM | For tasks that need to run twice during business hours, such as mid-morning and late-afternoon updates. |
0 0 1,15 * * | On the 1st and 15th of every month at midnight | Useful for mid-month and end-of-month data reconciliation or reporting. |
0 0,6,12,18 * * * | Every day at 12 AM, 6 AM, 12 PM, 6 PM | For tasks needing to run four times a day at fixed intervals, ideal for periodic health checks or data aggregation. |
YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
Labelled Cron Expressions with Human-Readable Descriptions
This dataset provides a collection of common cron expressions, each paired with a clear, human-readable description and a note explaining its typical use case. It serves as a reference for developers to quickly understand or implement scheduling patterns. The accompanying tool allows for looking up these descriptions and parsing cron expressions into their constituent parts.
25 rows · category: reference · licence: CC0-1.0 (public domain)
Usage
from tool import load, get_by_cron, search
# Load all data
data = load()
print(f"Total entries: {len(data)}")
# Find entries for a specific cron expression
results = get_by_cron('* * * * *')
for r in results:
print(f"Cron: {r['input']} -> {r['label']}")
# Search by keyword
matches = search('backup')
for m in matches:
print(f"Match: {m['input']} - {m['label']}")
Sample rows
{"input": "* * * * *", "label": "Every minute", "note": "The most frequent possible schedule, often used for monitoring or very high-frequency tasks."}
{"input": "0 * * * *", "label": "Every hour on the hour", "note": "Common for hourly reports, data synchronization, or health checks."}
{"input": "0 0 * * *", "label": "Every day at midnight", "note": "Ideal for daily backups, data processing, or generating daily reports."}
Files
| File | What |
|---|---|
data.jsonl |
the dataset, one JSON object per line |
tool.py |
stdlib-only loader and helpers |
test_tool.py |
tests that pass against the data |
Source: https://github.com/simalidudu-boop/labelled-cron-expressions
Support
This is free and public domain. If it saved you time, zap it: SharkSkin@coinos.io
Generated and maintained by an autonomous pipeline. Issues and PRs welcome.
- Downloads last month
- 30