Cron expression explainer / Every 20 minutes

Cron expression for every 20 minutes: */20 * * * *

Runs at :00, :20 and :40, 72 times a day.

Every 20 minutes.

*/20
Minute
*
Hour
*
Day of month
*
Month
*
Day of week
Next 10 runs in
  1. Thu, Nov 19, 2026, 02:20
  2. Thu, Nov 19, 2026, 02:40
  3. Thu, Nov 19, 2026, 03:00
  4. Thu, Nov 19, 2026, 03:20
  5. Thu, Nov 19, 2026, 03:40
  6. Thu, Nov 19, 2026, 04:00
  7. Thu, Nov 19, 2026, 04:20
  8. Thu, Nov 19, 2026, 04:40
  9. Thu, Nov 19, 2026, 05:00
  10. Thu, Nov 19, 2026, 05:20
Run this on RunLaterRunLater calls your URL on this schedule, retries failures and logs every response. The schedule is filled in for you after sign-in. 14-day trial, Starter $15/month.

Field by field

  • */20minute
  • *hour: any value
  • *day of month: any value
  • *month: any value
  • *day of week: any value

Variations

  • */20 9-17 * * 1-5Every 20 minutes from 9:00 to 17:40, Monday to Friday
  • 5-59/20 * * * *Every 20 minutes, starting at minute 5 instead of 0
  • */20 * * * 1-5Every 20 minutes on weekdays only
  • 0 */20 * * * *Spring @Scheduled (seconds first): every 20 minutes
  • 0 0/20 * * * ?Quartz (seconds first, ? for day of week): every 20 minutes
  • cron(0/20 * * * ? *)AWS EventBridge (6 fields, with year): every 20 minutes

Questions

What is the cron expression for every 20 minutes?

*/20 * * * *. Every 20 minutes.

Which timezone will it run in?

Crontab on a server uses the server clock (often UTC). In RunLater you pick the timezone on each scheduled request, and daylight saving changes are handled for you.

Is */20 the same as 0/20?

In standard cron, */20 and 0-59/20 both mean minutes 0, 20, 40 and so on, 72 runs a day. 0/20 comes from Quartz and EventBridge syntax; some crontab versions reject it, so */20 is the safe choice.

Can GitHub Actions run every 20 minutes?

The syntax is allowed (the shortest interval is 5 minutes), but scheduled runs can start late or be dropped at busy times. In our own test a */15 schedule started a median of 4 minutes 23 seconds late.

What if the job fails?

Plain cron does not retry. RunLater retries a failed request (non-2xx or timeout) with exponential backoff, up to 10 retries, and logs every attempt with the status code and response body.

Call a URL every 20 minutes without running a server

Paste */20 * * * * into a RunLater scheduled request with your URL, method, headers and body. It runs in the timezone you choose, retries failures and logs every response.

Start a 14-day trialStarter is $15/month for 250 scheduled requests and 25,000 runs. Cancel before day 14 and you pay nothing.

Next steps: set up a cron job for a URL, pick the right timezone and see how failed runs are retried.

Other common schedules