Why */35 cron does not mean every 35 minutes

Follow the schedule across an hour boundary

Suppose your schedule starts before midnight UTC on 15 October 2026. The selected minute values are 0 and 35. After 00:35, the next selected minute is 01:00, only 25 minutes later. The counter has not continued to minute 70; a new hour has begun.

Enter */35 * * * * in the generator or Cron Parser. Read the minute-field expansion, not just a friendly sentence. The generator previews runs after the current instant; the following fixed timeline illustrates the same field rule.

Choose clock time or elapsed time

For a job that should run at consistent positions on the clock, cron is suitable. For example, */15 * * * * selects 00, 15, 30 and 45, producing uniform quarter-hour gaps because 15 divides 60.

For a requirement of 35 elapsed minutes after a previous start or completion, use an interval-capable scheduler. Define whether the interval begins at the start or end, whether missed runs catch up, and whether overlapping executions are allowed. A cron expression alone cannot enforce those rules.

Do not substitute */35 in a production job merely because a display says “every 35 minutes”. Check boundary cases for hour, day and month steps as well. Month lengths vary, so a day-field step is especially different from a fixed number of elapsed days.

Verify the next runs and execution policy

Record the expression, time zone, several upcoming instants and expected intervals. Then compare them with your actual scheduler using its own preview or logs. A successful parse in PageUtil proves only that the supported expression syntax was understood.

Test a missed-run and slow-job scenario separately. If a task lasts 40 minutes, an otherwise correct schedule may overlap. Use application-level locking or the scheduler’s concurrency controls when the work must run once.

Expression: */35 * * * *
Minute values: 0, 35
Consecutive gaps: 35, 25, 35, 25 minutes
Requirement: every 35 elapsed minutes → choose an interval scheduler

References

Use the linked specifications and product documentation to check behavior in your own environment.