Skip to content

feat(serverless): job triggers and multi schedule MTA-7157#6591

Open
Loic-kd wants to merge 2 commits into
mainfrom
MTA-7157
Open

feat(serverless): job triggers and multi schedule MTA-7157#6591
Loic-kd wants to merge 2 commits into
mainfrom
MTA-7157

Conversation

@Loic-kd

@Loic-kd Loic-kd commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Your checklist for this pull request

Description

Please describe what you added or changed.

@Loic-kd Loic-kd self-assigned this Jun 11, 2026
@Loic-kd Loic-kd requested review from a team as code owners June 11, 2026 15:03
@Loic-kd Loic-kd added do not merge PR that shouldn't be merged before a specific date (eg release) status: doc review Waiting for doc team review labels Jun 11, 2026

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.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

@vanda-scw vanda-scw Jun 12, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge PR that shouldn't be merged before a specific date (eg release) status: doc review Waiting for doc team review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants