Why validate your Cron expression?

Hidden risks

Cron The syntax “week” and “date” fields are in some contexts the relationship between logical “or” and in others the logical “and” relationship. This ambiguity often results in backup scripts, clean-up missions operating at unexpected times and exhausting server resources.

The need for the solver

Writes an expression is not enough, you need to see a specific time series for execution. This tool simulates the future by 5 The following implementation period allows you to make a visual determination of whether the plan is in line with operational needs and ensures the stability of the production environment.

How to read the Cron field?

A standard Linux Cron expression consists of five parts:

1 place (minutes) : 0-59。 If */5 , is executed every 5 minutes.
2nd bit (hours) : 0-23。 If 2,4,6 On behalf of the delegates, at 2 a.m., 4 a.m., 6 a.m.
3 Bit (date) : 1-31。 Representing the day of the month.
4th place (month) : 1-12。 Representing the month of the year.
5 places (weeks) : 0-6。 Note that 0 or 7 usually represents Sunday.

Common debugging cases

Case I: 30 minutes per hour 。 Should be configured as 30 * * * * 。 It's a regular story of a beginner. */30 * * * * That means it's done every half hour.
Case II: Run on a working day only 。 Configure As 0 9 * * 1-5 。 This ensures that your automated scripts do not disturb the server on weekends.
Case III: Complex clustering 。 Like 0 0 1,15 * * , represents the 1st and 15ths of the month running at midnight.

Technical advantages of this tool

Unlike a simple regular match, this tool contains a complete command simulation engine. It not only translates the grammar, but also seeks real future implementation points through algorithmic integrities, based on the current system time. Whatever the complexity of your expression (/), its scope (-) or its number (,) is, the result is precisely predicted.