---
title: "Discussion on \"Cron expression every 5 minutes, every 30 minutes, every hour: a cheat sheet that explains the fields\" | Hashnode"
description: "Discussion on \"Cron expression every 5 minutes, every 30 minutes, every hour: a cheat sheet that explains the fields\". Most people search for a cron expression, copy the first answer and move on. That works until the schedule runs at the wrong time, or the same expression is rejected by AWS or Spring. This cheat sheet"
url: "https://hashnode.com/posts/cron-expression-every-5-minutes-every-30-minutes-every-hour-a-cheat-sheet-that-explains-the-fields/6ae06deb1222d4e04d1cb50e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Cron expression every 5 minutes, every 30 minutes, every hour: a cheat sheet that explains the fields](https://delayrun.hashnode.dev/cron-expression-every-5-minutes-every-30-minutes-every-hour-a-cheat-sheet-that-explains-the-fields?utm_source=hashnode&utm_medium=feed)

Most people search for a cron expression, copy the first answer and move on. That works until the schedule runs at the wrong time, or the same expression is rejected by AWS or Spring. This cheat sheet

Oct 27 · 6 min read · delayrun.hashnode.dev  
Updated Oct 31  
Read the article

-   [#cron](https://hashnode.com/tag/cron)
-   [#devops](https://hashnode.com/tag/devops)
-   [#backend](https://hashnode.com/tag/backend)
-   [#linux](https://hashnode.com/tag/linux)

## Written by

[delay.run](https://hashnode.com/@delayrun)

@delayrun

  
[View profile](https://hashnode.com/@delayrun)

Hosted cron jobs over plain HTTP, with retries, run logs and alerts.

delay.run calls your URL on a cron schedule, after a delay, or right away from one API call. No SDK and no server to maintain. Every run is logged with its request and response, failed jobs are retried with backoff, and alerts go to email, Slack or Discord. Starts with 1,000 free requests. https://delay.run

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
