Cron expression explainer / Every 2 minutes
Cron expression for every 2 minutes: */2 * * * *
Runs on every even minute, 720 times a day.
Every 2 minutes.
- Thu, Nov 19, 2026, 02:10
- Thu, Nov 19, 2026, 02:12
- Thu, Nov 19, 2026, 02:14
- Thu, Nov 19, 2026, 02:16
- Thu, Nov 19, 2026, 02:18
- Thu, Nov 19, 2026, 02:20
- Thu, Nov 19, 2026, 02:22
- Thu, Nov 19, 2026, 02:24
- Thu, Nov 19, 2026, 02:26
- Thu, Nov 19, 2026, 02:28
Field by field
- */2minute
- *hour: any value
- *day of month: any value
- *month: any value
- *day of week: any value
Variations
- */2 9-17 * * 1-5Every 2 minutes from 9:00 to 17:58, Monday to Friday
- 1-59/2 * * * *Every 2 minutes, starting at minute 1 instead of 0
- */2 * * * 1-5Every 2 minutes on weekdays only
- 0 */2 * * * *Spring @Scheduled (seconds first): every 2 minutes
- 0 0/2 * * * ?Quartz (seconds first, ? for day of week): every 2 minutes
- cron(0/2 * * * ? *)AWS EventBridge (6 fields, with year): every 2 minutes
Questions
What is the cron expression for every 2 minutes?
*/2 * * * *. Every 2 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 */2 the same as 0/2?
In standard cron, */2 and 0-59/2 both mean minutes 0, 2, 4 and so on, 720 runs a day. 0/2 comes from Quartz and EventBridge syntax; some crontab versions reject it, so */2 is the safe choice.
Can GitHub Actions run every 2 minutes?
No. The shortest interval GitHub Actions allows is 5 minutes.
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 2 minutes without running a server
Paste */2 * * * * 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.
Next steps: set up a cron job for a URL, pick the right timezone and see how failed runs are retried.