గణితం ఎలా పనిచేస్తుంది
Each of the five fields is expanded into the set of values it allows: an asterisk becomes the entire range, 1-5 a range, */15 a step, and 1,15,30 a list. Next fire times are then found by brute force, walking forward one minute at a time from now, converting each candidate into your selected timezone and testing set membership, up to one year ahead. A 7 in the day-of-week field is normalised to 0 for Sunday.
Mode switches between Parse / translate, where you paste an expression (the default is */15 9-17 * * 1-5), and Visual builder, which offers five separate boxes joined back into a single string. The Timezone dropdown matters more than it appears: it changes only the next-fire list, so the same expression produces different clock times for a UTC server and your local zone. Seven presets cover Every minute through Sunday midnight.
This parser handles 5-field Unix crontab and nothing else. Six- and seven-field Quartz or AWS EventBridge expressions are rejected outright, as are the extensions many schedulers add: L, W, #, question-mark day fields, @daily-style shorthands, and three-letter names such as MON or JAN. Field values are not bounds-checked either, so 99 * * * * parses happily and simply never fires. The plain-English description is always rendered in English regardless of page language.
తరచుగా అడిగే ప్రశ్నలు
What does */15 9-17 * * 1-5 actually mean? +
That is the default expression: every 15 minutes, during hours 9 through 17, Monday to Friday. It fires at :00, :15, :30 and :45 of each of those hours, which the next-fire table confirms in whichever timezone you have selected.
If I set both day-of-month and day-of-week, must both match? +
No. When both fields are restricted, cron fires when either matches, and this tool implements that Unix standard. If only one of the two is restricted, that field alone decides. Leaving both as asterisks means every day.
Is Sunday 0 or 7 in a cron expression? +
Both work here. Any 7 in the day-of-week field is rewritten to 0 before parsing, so 0 0 * * 0 and 0 0 * * 7 describe the same Sunday-midnight schedule. The visual builder labels that field Day of week (0=Sun).
Which timezone are the next fire times shown in? +
Whichever you choose in the Timezone dropdown, which starts on your browser's own zone and is populated from your browser's timezone database. Bear in mind that cron on a server normally follows that machine's clock, not yours, so pick accordingly.
Why does my cron expression come back as invalid? +
The parser demands exactly five whitespace-separated fields containing numbers, ranges, steps or lists. Six-field Quartz strings, @hourly shorthands and name forms such as JAN or MON all fail, and the error message tells you how many fields it actually counted.
