Conversation
|
|
||
| 1. Click **Jobs** in the **Serverless** section of the side menu. The jobs page displays. | ||
|
|
||
| 2. Click the name of the job you want to manage, then click the **Triggers** tab. |
There was a problem hiding this comment.
| 2. Click the name of the job you want to manage, then click the **Triggers** tab. | |
| 2. Click the name of the job you want to delete, then click the **Triggers** tab. |
|
|
||
| ## Job trigger | ||
|
|
||
| A job trigger allows you to invoke Jobs automatically at a specific time on a recurring cron schedule. It works similarly to a traditional Linux cron job, using the `* * * * *` format. Refer to our [cron schedules reference](/serverless-jobs/reference-content/cron-schedules/) for more information. You can add multiple triggers on the same Job Definition and also set [command and arguments](/serverless-jobs/concepts/#commands-and-arguments) specifically for one trigger to override the default command and arguments of your job at runtime. |
There was a problem hiding this comment.
Either "... and also set [commands and arguments] ..."
or "... and also set a [command and arguments] ..."
Also, I believe the anchor has to change to: #commands-arguments-deprecated (because the heading was changed). However, if you accept my advice and you don't add "(deprecated)", then in that case, there is no need to change the anchor, of course.
| ## Time zones | ||
|
|
||
| - Serverless Jobs allow modifying the time zone of their schedules via the Job **Settings** tab. Refer to [the job scheduling documentation](/serverless-jobs/how-to/manage-job-schedule/) for more information. | ||
| - Serverless Jobs allow modifying the time zone of their schedules via the Job **Settings** tab. Refer to [the job triggers documentation](/serverless-jobs/how-to/manage-job-triggers/) for more information. |
There was a problem hiding this comment.
Isn't it done via the Triggers tab (and not the Settings tab)?
| import ServerlessConcepts from '@macros/serverless/serverless-concepts.mdx' | ||
|
|
||
| ## Commands and arguments | ||
| ## Commands and arguments (deprecated) |
There was a problem hiding this comment.
I think I wouldn't add "(deprecated)". It gives the impression as if commands and arguments had been deprecated. They are still in use, you can still set up commands and arguments. You just use different fields for this purpose.
Your checklist for this pull request
Description
Please describe what you added or changed.