added cron tutorial #1515

macolso · 2025-04-02T03:41:30Z

Content must go through a pre-merge checklist.

Resolves https://github.com/fermyon/a3000-docs/issues/228

Blocked on #1514

Pre-Merge Content Checklist

This documentation has been checked to ensure that:

The title, template, and date are all set
Does this PR have a new menu item (anywhere in templates/*.hbs files) that points to a document .md that is set to publish in the future? If so please only publish the .md and .hbs changes in real-time (otherwise there will be a menu item pointing to a .md file that does not exist)
File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep $'\r' | wc -l and expect 0 as a result)
Has passed bart check
Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)
Headings are using Title Case
Code blocks have the programming language set to properly highlight syntax and the proper copy directive
Have tested with npm run test and resolved all errors
Relates to an existing (potentially outdated) blog article? If so please add URL in blog to point to this content.

Signed-off-by: macolso <[email protected]>

itowlson · 2025-04-02T03:52:15Z

FWIW I would not block this on updating the command reference but we would want to update the plugin install instructions so people get the 0.3 version.

itowlson · 2025-04-02T03:53:57Z

content/wasm-functions/using-cron-trigger.md

+- [Next Steps](#next-steps)

-This tutorial guides you through the process of scheduling HTTP requests in a Spin application running on Fermyon Wasm Functions using cron jobs. The `spin aka cron` command allows applications to receive scheduled HTTP triggers without relying on external services. In this tutorial, you'll learn how to define and manage cron jobs using the `spin aka cron` command.
+This tutorial guides you through the process of scheduling HTTP requests in a Spin application running on Fermyon Wasm Functions using cron jobs. The `spin aka crons` command allows applications to receive scheduled HTTP triggers without relying on external services. In this tutorial, you'll learn how to define and manage cron jobs using the `spin aka crons` command.


spin aka cron is allowed and may be less jarring.

(I rather feel the long form should be spin aka cronjobs. I've never heard crons as a plural before. But maybe I just mix in the wrong circles!)

We can also consider changing the plugin if we all agree that the nomenclature is off. We did not think long and hard about the most appropriate name. Considering the functionality is labeled as experimental, breaking changes are probably fine.

I also lean towards cron -- feels a bit more natural.

Also a good reminder I should flag that this feature is experimental in the tutorial

content/wasm-functions/using-cron-trigger.md

itowlson · 2025-04-02T03:57:06Z

content/wasm-functions/using-cron-trigger.md

+# Create Spin application 

-Spin is a lightweight framework for building WebAssembly microservices and applications. It allows developers to define cron jobs that execute functions at scheduled intervals. To simplify development, Spin provides templates for various use cases, including scheduled tasks. 
+You must have a running Spin application on Fermyon Wasm Functions to apply the cron trigger to. We'll create a new Spin application for scheduling tasks using cron jobs using the `http-js` template:


The application isn't "for" scheduling tasks is it?

You're right - it's not intended for scheduling tasks but the wording is a bit misleading. I've reworded this sentence.

itowlson · 2025-04-02T03:58:20Z

content/wasm-functions/using-cron-trigger.md

+```

-## Creating a Cron Job for your Spin application
+We'll go ahead add a specific path for our cron trigger in later steps:


It's a HTTP trigger which we will run from a cron job. Sorry for the pedantry but "cron trigger" is a specific thing and if we say this is a cron trigger we will cause a measurable muddle!

content/wasm-functions/using-cron-trigger.md

itowlson · 2025-04-02T04:03:07Z

content/wasm-functions/using-cron-trigger.md

+
+Now we will use the `spin aka crons` command to invoke the Spin app's HTTP endpoint at our desired interval. The syntax for this request follows standard crontab format.
+
+> `spin aka cron` supports single digits in each cron expression field and intervals in every position except the day of the week (e.g., `* */12 * * *` for every 12 hours). The smallest supported cron configuration is every 5 minutes (`*/5 * * * *`). Other syntax elements like comma-separated lists and ranges are not supported. Please feel free to[leave feedback](https://fibsu0jcu2g.typeform.com/to/G2u4tPcP) if your desired range is not supported. 


Is "single digits" correct? You can't use double-digit numbers for e.g. day of month or hour of day?

You can, and the point about comma separated lists and ranges (which is from the original cron proposal) is actually not currently correct (they are supported). See my previous point about how we're currently allowing anything that happens to work with the libraries we're using, and we need to be a bit more strict about it.

itowlson · 2025-04-02T04:03:35Z

content/wasm-functions/using-cron-trigger.md

+
+# Creating a Cron Job for Your Spin Application
+
+Now we will use the `spin aka crons` command to invoke the Spin app's HTTP endpoint at our desired interval. The syntax for this request follows standard crontab format.


Link to the dialect of the crontab format that we support

Unfortunately I've not been able to find a good, concise explainer of the syntax we support. We might want to simply write it out here. The unfortunate truth is that currently the exact syntax we support is a bit of an implementation detail. We should limit the syntax for now so that we don't accidentally support something we hadn't originally planned on.

itowlson · 2025-04-02T04:07:21Z

content/wasm-functions/using-cron-trigger.md

+
+> `spin aka cron` supports single digits in each cron expression field and intervals in every position except the day of the week (e.g., `* */12 * * *` for every 12 hours). The smallest supported cron configuration is every 5 minutes (`*/5 * * * *`). Other syntax elements like comma-separated lists and ranges are not supported. Please feel free to[leave feedback](https://fibsu0jcu2g.typeform.com/to/G2u4tPcP) if your desired range is not supported. 
+
+Let's create a cron job that runs every hour. Since scheduling is based on UTC, you may need to [convert your local time to UTC](https://www.worldtimebuddy.com/?pl=1&lid=100&h=100&hf=1) to ensure correct execution.


I'm not sure why local/UTC would matter for an "every hour" schedule? I'm guessing it's that the schedule is "every hour on the hour" and you're thinking about half-hour timezone offsets? Like okay I convert my local time to UTC, it's 5:08am or whatever, now what do I do with that result?

It may be better to pull out the "times are in UTC" comment to go with the scheduling/crontab discussion perhaps?

itowlson · 2025-04-02T04:09:53Z

content/wasm-functions/using-cron-trigger.md

+<!-- @selectiveCpy -->
+
+```console
+spin aka crons create "0 * * * *" "/hello" "hello-cron-job"


Maybe explain what these fields are, since they are not named in the command. I'm guessing the second is the route to be hit. Is the third the name of the app to be hit? Or the name of the job? (In which case how does it know which app to hit? Is this an "app in current directory" thing?)

If the third parameter is not the name of the app, it would be good to choose a different string from the name of the app, so as to avoid ambiguity.

The syntax is spin aka crons create $SCHEDULE $PATH_AND_QUERY $NAME_OF_CRON

Indeed the app that will be hit is the "current app".

rylev · 2025-04-02T08:19:21Z

content/wasm-functions/using-cron-trigger.md

+- [Next Steps](#next-steps)

-This tutorial guides you through the process of scheduling HTTP requests in a Spin application running on Fermyon Wasm Functions using cron jobs. The `spin aka cron` command allows applications to receive scheduled HTTP triggers without relying on external services. In this tutorial, you'll learn how to define and manage cron jobs using the `spin aka cron` command.
+This tutorial guides you through the process of scheduling HTTP requests in a Spin application running on Fermyon Wasm Functions using cron jobs. The `spin aka crons` command allows applications to receive scheduled HTTP triggers without relying on external services. In this tutorial, you'll learn how to define and manage cron jobs using the `spin aka crons` command.


We can also consider changing the plugin if we all agree that the nomenclature is off. We did not think long and hard about the most appropriate name. Considering the functionality is labeled as experimental, breaking changes are probably fine.

content/wasm-functions/using-cron-trigger.md

rylev · 2025-04-02T08:25:24Z

content/wasm-functions/using-cron-trigger.md

+
+## Deploy Spin Application to Fermyon Wasm Functions
+
+Before applying our cron trigger, we must have our Spin application running on the Fermyon Wasm Functions platform. Deploy the application with:


+1 to rewording away from "trigger". I would also use the terminology of "scheduling" versus "applying".

rylev · 2025-04-02T08:35:23Z

content/wasm-functions/using-cron-trigger.md

+
+# Creating a Cron Job for Your Spin Application
+
+Now we will use the `spin aka crons` command to invoke the Spin app's HTTP endpoint at our desired interval. The syntax for this request follows standard crontab format.


Unfortunately I've not been able to find a good, concise explainer of the syntax we support. We might want to simply write it out here. The unfortunate truth is that currently the exact syntax we support is a bit of an implementation detail. We should limit the syntax for now so that we don't accidentally support something we hadn't originally planned on.

rylev · 2025-04-02T08:37:12Z

content/wasm-functions/using-cron-trigger.md

+
+Now we will use the `spin aka crons` command to invoke the Spin app's HTTP endpoint at our desired interval. The syntax for this request follows standard crontab format.
+
+> `spin aka cron` supports single digits in each cron expression field and intervals in every position except the day of the week (e.g., `* */12 * * *` for every 12 hours). The smallest supported cron configuration is every 5 minutes (`*/5 * * * *`). Other syntax elements like comma-separated lists and ranges are not supported. Please feel free to[leave feedback](https://fibsu0jcu2g.typeform.com/to/G2u4tPcP) if your desired range is not supported. 


You can, and the point about comma separated lists and ranges (which is from the original cron proposal) is actually not currently correct (they are supported). See my previous point about how we're currently allowing anything that happens to work with the libraries we're using, and we need to be a bit more strict about it.

rylev · 2025-04-02T08:39:07Z

content/wasm-functions/using-cron-trigger.md

+<!-- @selectiveCpy -->
+
+```console
+spin aka crons create "0 * * * *" "/hello" "hello-cron-job"


The syntax is spin aka crons create $SCHEDULE $PATH_AND_QUERY $NAME_OF_CRON

Indeed the app that will be hit is the "current app".

content/wasm-functions/using-cron-trigger.md

templates/functions_sidebar.hbs

sidebar changes, header tweaks, few verbiage updates Co-authored-by: Ryan Levick <[email protected]> Co-authored-by: itowlson <[email protected]> Signed-off-by: MacKenzie Olson <[email protected]>

itowlson · 2025-04-03T22:18:09Z

@macolso it occurred to me that one question with this is "how do I know it worked?" What does the reader see if they follow the tutorial? Can they see the HTTP responses in cron logs, for example?

(If not, what is the simplest example app that they can cron and still see an observable result? A silly example might be: an app with two routes: /cron-me increments a value in KV storage, and /count-me responds with a message like "I've been cronned N times." So the cron job could hit /cron-me, and the user could curl /count-me to see the value increment over time. I realise this makes the tutorial more complicated, and distracts from the focus on the cron job though.)

Signed-off-by: macolso <[email protected]>

macolso · 2025-04-11T20:35:39Z

@itowlson I had a similar niggle with this tutorial. You can actually see the HTTP responses in the cron logs! I've updated the sample application to log cron events, inferring whether it's a cron event or a direct ping based on the presence of a query parameter. Let me know if this feels like a hacky solution, and I can remove that nuance.

itowlson

Thanks for the update @macolso - this is much clearer now - unfortunately I still have a few niggles and typos, and at least one thing which I'm pretty sure is an error. Sorry for being picky!

itowlson · 2025-04-13T20:57:35Z

content/wasm-functions/using-cron-jobs.md

+        // Capture current timestamp for logging and response
+        const now = new Date().toISOString();
+
+        // Log the trigger event, including the value of 'msg'


This only appears to log in the cron case - should the comment be moved inside the if?

I decided to simplify the example and remove the functionality that changes the output depending on whether the app received a direct ping or a cron trigger. I agree that the added complexity outweighs the value it's providing.

itowlson · 2025-04-13T20:58:40Z

content/wasm-functions/using-cron-jobs.md

+        const now = new Date().toISOString();
+
+        // Log the trigger event, including the value of 'msg'
+        if (msg) {


Having two code paths complicates the application. The application isn't the core point of the tutorial, it's just something we need to have, so I'd keep it as simple as possible. It already has routing for the cron-me URL which is more than enough complexity I reckon...

itowlson · 2025-04-13T21:03:56Z

content/wasm-functions/using-cron-jobs.md

+
+```console
+spin aka logs -a hello-cron-job
+2025-04-02 04:00:00 [hello-cron-job]  Hello, cron job triggered with msg: "fwf" at 2025-04-12T04:00:00Z


Consider linking this back to the console.log statement from from the HTTP application, and maybe put some more motivation around this, both here and when you write the application. E.g. motivating the application a la "For a real cron job, you'd see its effects in the data it updates or the artifacts it produces. For this tutorial, though, we'll just emit a log, so that we can see the application has been called." and then down here we can say "This is the message we had the application log so that we could see it was being called" or something like that.

(If you keep the "different behaviour when they try it interactively" thing then it would be good to be extra clear about this because the message will be unfamiliar.)

Great suggestion! I added a disclaimer above the source code snippet that this is a simplified example and allude to what operations you may see in a real world example.

content/wasm-functions/using-cron-jobs.md

itowlson · 2025-04-13T21:05:55Z

content/wasm-functions/using-cron-jobs.md

+
+* **Schedule:** How often the job runs, using standard cron syntax
+* **Path and query:** The HTTP path (and optional query parameters) to invoke
+* **Name:** The Spin applciaton to apply the cron job to


Suggested change

* **Name:** The Spin applciaton to apply the cron job to

* **Name:** The Spin application to apply the cron job to

itowlson · 2025-04-13T21:09:58Z

content/wasm-functions/using-cron-jobs.md

+
+* **Schedule:** How often the job runs, using standard cron syntax
+* **Path and query:** The HTTP path (and optional query parameters) to invoke
+* **Name:** The Spin applciaton to apply the cron job to


The plugin docs say that the third parameter is the name of the cron job not the name of the application.

(If that's true, we need to explain which application it's going to hit - I assume the one in the current directory.)

(ETA: see Ryan's earlier comment #1515 (comment))

Good catch. I've updated accordingly.

itowlson · 2025-04-13T21:12:45Z

content/wasm-functions/using-cron-jobs.md

+
+Now we will use the `spin aka crons` command to invoke the Spin app's HTTP endpoint on our desired schedule. The syntax for this request follows standard crontab format.
+
+> `spin aka crons` supports multiple digits in each cron expression field and intervals in every position (e.g., `* */12 * * *` for every 12 hours). Syntax elements like comma-separated lists and ranges are currently supported. Scheduling follows UTC and you may need to [convert your local time to UTC](https://www.worldtimebuddy.com/?pl=1&lid=100&h=100&hf=1) to ensure correct execution during daylight savings time.


Won't I need to convert my local time to UTC anyway, if I want it to fire at a particular local time? And then amend it at each DST change?

Yes, that's a good point. I liked your language suggestion below -- I will make that modification.

content/wasm-functions/using-cron-jobs.md

itowlson · 2025-04-13T21:19:30Z

content/wasm-functions/using-cron-trigger.md

+- [Next Steps](#next-steps)

-This tutorial guides you through the process of scheduling HTTP requests in a Spin application running on Fermyon Wasm Functions using cron jobs. The `spin aka cron` command allows applications to receive scheduled HTTP triggers without relying on external services. In this tutorial, you'll learn how to define and manage cron jobs using the `spin aka cron` command.
+This tutorial guides you through the process of scheduling HTTP requests in a Spin application running on Fermyon Wasm Functions using cron jobs. The `spin aka crons` command allows applications to receive scheduled HTTP triggers without relying on external services. In this tutorial, you'll learn how to define and manage cron jobs using the `spin aka crons` command.


This page seems to be largely the same content as the previous one but with the "cron trigger" language back in... is this meant to have been deleted in favour of the page above? The TOC entry still points to this one.

Yes, using-cron-triggers.md should be deleted and the sidebar should be updated to point at using-cron-jobs.md

itowlson · 2025-04-13T21:26:28Z

content/wasm-functions/using-cron-jobs.md

+spin aka deploy
+```
+
+Upon successful deployment, you should receive a domain name that you can use to test the application:


Consider shoiwing the deploy output so they can see where to find the domain name.

Added, good suggestion!

Signed-off-by: macolso <[email protected]>

macolso · 2025-04-15T21:22:28Z

@itowlson Excellent feedback—thank you! I've taken another stab at addressing the concerns. I think it flows much better now, and I agree that the simplified example makes it easier to read and keeps the user focused on the task at hand. Let me know what you think

itowlson

Thanks @macolso - I agree that this flows better - unfortunately I did get confused at one point, and spotted a couple of what I think were typos arising from the previous reuse of names. I may be wrong though...

itowlson · 2025-04-15T21:37:58Z

content/wasm-functions/using-cron-jobs.md

+
+We'll go ahead add a path that will be used our cron job in later steps:
+
+```toml


Do we need to add a second trigger? Is this trying to illustrate a recommended practice? It would be good to say more about the motivation because right now this feels like a step I follow without knowing why.

I went back and forth on this... I decided to not add a second trigger to keep the example simple. Perhaps I can write a more realistic example for Spin Hub that we can link as a resource at the end of the tutorial for those interested in that scenario.

To simplify things, I've removed the specific path and replaced it with wildcard.

itowlson · 2025-04-15T21:43:10Z

content/wasm-functions/using-cron-jobs.md

+component = "hello-cron-job"
+```
+
+> Note that you can have multiple cron jobs per Spin application as long as the combination of schedule and path_and_query is unique. We will review how to set those values later in the tutorial.  


This seems a bit disconnected from "add a trigger." It feels like you're setting up for a mental model of "multiple cron jobs per app, each cron job handled by a different component, those components on different triggers, cron jobs mapped to components via their routes" but it's not explicit, and the "each trigger points at the same component as the everything route and we route within the component" doesn't draw out that structure.

Perhaps move this down to where you talk about creating cron jobs, and if you want to talk about how to structure a multi-job app then do so there? And focus on the simple "get something working" path here? Or do you feel that leads readers to a dead end?

Agreed - I've moved it down to the section where I talk about the required parameters for the spin aka crons create subcommand. I decided to not expand into multi-job to keep the tutorial manageable, but I like the idea of creating a more complex example for Spin Hub or fwf-examples we can link to in this tutorial for those wanting a more realistic example.

itowlson · 2025-04-15T21:48:33Z

content/wasm-functions/using-cron-jobs.md

+
+* **Schedule** – How often the job runs, in standard cron syntax
+* **Path and query** – The HTTP path (and optional query parameters) to invoke
+* **Name** – A name for your cron job (this will be associated with the Spin application in your current working directory)


Consider breaking this up - "it applies to the app in your current directory" is important enough that it shouldn't be a parenthesis under "the name for the job". E.g.

Suggested change

* **Name** – A name for your cron job (this will be associated with the Spin application in your current working directory)

* **Name** – A name for your cron job

The cron job will always invoke the Spin application in your current working directory.

(or perhaps "...will always invoke the Spin application deployed from your current..." which avoids any implication that it will invoke it in your cwd, but is perhaps awkward and requires extra effort for the reader to parse, not sure)

Good point about highlighting this. I removed it from parenthesis and put it at the beginning of the paragraph for this section.

itowlson · 2025-04-15T21:49:36Z

content/wasm-functions/using-cron-jobs.md

+----------------+--------------+-------------------------+
+| Name           | Schedule     | Next Run                |
+=========================================================+
+| hello-cron-job |  */5 * * * * | 2025-04-02 04:00:00 UTC |


Suggested change

| hello-cron-job | */5 * * * * | 2025-04-02 04:00:00 UTC |

| cron-job-1 | */5 * * * * | 2025-04-02 04:00:00 UTC |

or wait, are you saying this is the app name rather than the job name?

(I am not sure if the command shows all cron jobs or only the ones associated with the current app.)

d'oh - typo! I fixed this. I also renamed the app to "hello-world" to avoid confusion between app name and cron job name.

I am not sure if the command shows all cron jobs or only the ones associated with the current app.)
@rylev any guidance on this? I'm not sure

Having thoroughly distinct different names for the app and the cron job is an excellent idea - thank you!

content/wasm-functions/using-cron-jobs.md

…s down, fixed cron typo Signed-off-by: macolso <[email protected]>

itowlson

This looks good to me. I'm happy to defer the "does it list all jobs or current app's jobs" if you want to get this done and dusted, it's a fairly minor detail and we can always add it later if the spirit moves us. (Although it may be worth waiting for Ryan anyway!) Thanks for your patience through the review cycles!

content/wasm-functions/using-cron-jobs.md

Co-authored-by: itowlson <[email protected]> Signed-off-by: MacKenzie Olson <[email protected]>

macolso · 2025-04-16T22:58:10Z

This looks good to me. I'm happy to defer the "does it list all jobs or current app's jobs" if you want to get this done and dusted, it's a fairly minor detail and we can always add it later if the spirit moves us. (Although it may be worth waiting for Ryan anyway!) Thanks for your patience through the review cycles!

Thanks for all the polish help! Between writing most of this at conferences or on plane, it definitely needed the help... I will go ahead and merge and we can add the "does it list all jobs or current app's jobs" later. I think it would be helpful to maybe even include an article about the purpose of that config file in our docs since it's a bit of an "insider knowledge" resource ATM.

added cron tutorial

c920afb

Signed-off-by: macolso <[email protected]>

itowlson reviewed Apr 2, 2025

View reviewed changes

itowlson mentioned this pull request Apr 2, 2025

Install aka plugin from registry #1516

Merged

9 tasks

rylev reviewed Apr 2, 2025

View reviewed changes

Apply suggestions from code review

da629da

sidebar changes, header tweaks, few verbiage updates Co-authored-by: Ryan Levick <[email protected]> Co-authored-by: itowlson <[email protected]> Signed-off-by: MacKenzie Olson <[email protected]>

updated example to give log cron events

e277383

Signed-off-by: macolso <[email protected]>

itowlson requested changes Apr 13, 2025

View reviewed changes

simplified example and fixed typos, improved clarity of language

6411001

Signed-off-by: macolso <[email protected]>

itowlson reviewed Apr 15, 2025

View reviewed changes

simplifed example by removing path, bumped query and path requirement…

49ce264

…s down, fixed cron typo Signed-off-by: macolso <[email protected]>

itowlson approved these changes Apr 16, 2025

View reviewed changes

content/wasm-functions/using-cron-jobs.md Outdated Show resolved Hide resolved

Update content/wasm-functions/using-cron-jobs.md

1ab1b82

Co-authored-by: itowlson <[email protected]> Signed-off-by: MacKenzie Olson <[email protected]>

macolso merged commit 8a830eb into fermyon:main Apr 16, 2025
3 checks passed


		Now we will use the `spin aka crons` command to invoke the Spin app's HTTP endpoint at our desired interval. The syntax for this request follows standard crontab format.

		> `spin aka cron` supports single digits in each cron expression field and intervals in every position except the day of the week (e.g., `* /12 * ` for every 12 hours). The smallest supported cron configuration is every 5 minutes (`/5 * * * *`). Other syntax elements like comma-separated lists and ranges are not supported. Please feel free to[leave feedback](https://fibsu0jcu2g.typeform.com/to/G2u4tPcP) if your desired range is not supported.


		# Creating a Cron Job for Your Spin Application

		Now we will use the `spin aka crons` command to invoke the Spin app's HTTP endpoint at our desired interval. The syntax for this request follows standard crontab format.


		> `spin aka cron` supports single digits in each cron expression field and intervals in every position except the day of the week (e.g., `* /12 * ` for every 12 hours). The smallest supported cron configuration is every 5 minutes (`/5 * * * *`). Other syntax elements like comma-separated lists and ranges are not supported. Please feel free to[leave feedback](https://fibsu0jcu2g.typeform.com/to/G2u4tPcP) if your desired range is not supported.

		Let's create a cron job that runs every hour. Since scheduling is based on UTC, you may need to [convert your local time to UTC](https://www.worldtimebuddy.com/?pl=1&lid=100&h=100&hf=1) to ensure correct execution.


		## Deploy Spin Application to Fermyon Wasm Functions

		Before applying our cron trigger, we must have our Spin application running on the Fermyon Wasm Functions platform. Deploy the application with:

	* Name: The Spin applciaton to apply the cron job to
	* Name: The Spin application to apply the cron job to


		Now we will use the `spin aka crons` command to invoke the Spin app's HTTP endpoint on our desired schedule. The syntax for this request follows standard crontab format.

		> `spin aka crons` supports multiple digits in each cron expression field and intervals in every position (e.g., `* /12 * *` for every 12 hours). Syntax elements like comma-separated lists and ranges are currently supported. Scheduling follows UTC and you may need to [convert your local time to UTC](https://www.worldtimebuddy.com/?pl=1&lid=100&h=100&hf=1) to ensure correct execution during daylight savings time.


		We'll go ahead add a path that will be used our cron job in later steps:

		```toml

	\| hello-cron-job \| /5 * * * \| 2025-04-02 04:00:00 UTC \|
	\| cron-job-1 \| /5 * * * \| 2025-04-02 04:00:00 UTC \|

added cron tutorial #1515

added cron tutorial #1515

Uh oh!

Conversation

macolso commented Apr 2, 2025

Pre-Merge Content Checklist

Uh oh!

itowlson commented Apr 2, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

macolso Apr 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

itowlson commented Apr 3, 2025

Uh oh!

macolso commented Apr 11, 2025

Uh oh!

itowlson left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

macolso Apr 3, 2025 •

edited

Loading