Sep 17, 2024 · Sep 16, 2024 · Sep 17, 2024 · Sep 17, 2024
diff --git a/_docs/pipelines/triggers/cron-triggers.md b/_docs/pipelines/triggers/cron-triggers.md

 Integrate additional settings in the Cron trigger such as simulating a Git event to enrich pipelines with repository details, adding/customizing environment variables, and caching, volume reuse, and notification configurations for the build.

 By integrating these additional options, Cron triggers can initiate pipeline executions at the predefined time intervals and at the same time populate the pipeline with repo and branch information from the Git trigger, required environment variables, and specialized behavior, for the build.
 By integrating these additional options, Cron triggers can initiate pipeline executions at the predefined time intervals, and at the same time populate the pipeline with repo and branch information from the Git trigger, required environment variables, and specialized behavior for the build.

 Create and manage Cron triggers for pipelines through [Codefresh UI](#cron-triggers-in-codefresh-ui), as described in this article.
 For the specifications, see [Cron trigger specifications in pipelines]({{site.baseurl}}/docs/integrations/codefresh-api/#cron-triggers).

 >**NOTE**
 Cron triggers are created in the UTC timezone.

 ## Legacy Cron triggers in Codefresh

 ##  Legacy Cron triggers in Codefresh
 If you see Cron triggers for your pipeline tagged with {::nomarkdown}<img src="../../../../images/icons/icon-warning.png" display=inline-block">{:/} tag, it indicates that you are using the legacy version.

 {% include image.html
 max-width="60%"
 %}

 **Migrate legacy trigger**
 * Click the **Edit** icon to view the trigger.
 * To migrate, click **Convert**.
 ##### Migrate legacy Cron triggers

 1. Click the **Edit** icon to view the trigger.
 1. To migrate, click **Convert**.
  Codefresh migrates the legacy Cron trigger and displays a `Trigger updated successfully` message.

 {% include image.html
 lightbox="true"
 alt="Migrate legacy Cron trigger in Codefresh UI"
 max-width="60%"
 %}
  Codefresh migrates the legacy Cron trigger and displays a Trigger updated successfully message.
 * Open the trigger displays the Settings tab with additional options.

 {:start="3"}
 1. Open the trigger displays the Settings tab with additional options.

  {% include image.html
 lightbox="true"
 max-width="60%"
 %}


 ## Cron triggers in Codefresh UI

 Create and manage Cron triggers for pipelines in the Codefresh UI.

 There are two parts to creating a Cron trigger in the UI:

 1. Defining the schedule for the trigger
  To learn about supported `cron` expression formats and aliases, see [Cron expression formats](#cron-expression-formats) in this article.
 1. (Optional) Selecting additional options:
  * Git trigger event to simulate when the Cron trigger timer is activated. The pipeline is populated with the information from the Git repo such as the repo URL, branch name, latest commit information, including the date and author of the commit.
  * Variables to populate for the build
  * Caching, volume reuse and notification behavior to override for the build

    * Git trigger event to simulate when the Cron trigger timer is activated. The pipeline is populated with the information from the Git repo such as the repo URL, branch name, latest commit information, including the date and author of the commit.
    * Variables to populate for the build.
    * Caching, volume reuse and notification behavior to override for the build.

 ## Create a Cron trigger in UI

 ## How to: Create a Cron trigger in UI
 **Before you begin**
 ##### Before you begin

 Review:
 * [Git trigger settings]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/#git-trigger-settings)
 * [Git trigger settings]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/#git-trigger-settings)
 * [Working with Git triggers]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/#working-with-git-triggers)
 * [Cron expression formats](#cron-expression-formats)

 **How to**
 #####How to

 1. In the Codefresh UI, from the sidebar, select **Pipelines**.
 1. Select the pipeline to which to add the trigger, and then click the **Workflow** tab.
 url="/images/pipeline/triggers/add-trigger-dialog.png"
 caption="Select trigger type to add"
 alt="Select trigger type to add"
 max-width="60%"
 max-width="50%"
 %}

 {:start="5"}
 url="/images/pipeline/triggers/cron/cron-timer-tab.png"
 caption="Cron trigger: Cron Interval settings"
 alt="Cron trigger: Cron Interval settings"
 max-width="60%"
 max-width="50%"
 %}

 {:start="6"}
 1. Click **Settings**.
 1. Define the Git trigger simulation options:
    1. From the **Simulate Trigger From** drop-down list, select the type of Git trigger to simulate.
      The list displays all the Git triggers defined for the pipeline.
      The list displays all the Git triggers defined for the pipeline.
    1. From the **Select Branch** drop-down list, select the branch of the repository for this build.
 1. Expand **Variables**, and add or modify [environment variables]({{site.baseurl}}/docs/pipelines/variables/) for this build.
 1. Expand **Advanced Options** and select the overrides for this build. See [Advanced options]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/#advanced-settings-for-git-triggers).
 max-width="60%"
 %}

 {:start="7"}
 1. To confirm click **Done**.
  * If you defined only the Timer settings, the build is triggered according to the Cron expression.
  * If you defined both the Timer and additional Settings, the build is triggered according to the Cron expression, and depending on the settings, the pipeline is populated with the information from the Git repo, additional variables, and notifications when configured.

 {:start="10"}
 1. To confirm click **Done**.
    * If you defined only the Timer settings, the build is triggered according to the Cron expression.
    * If you defined both the Timer and additional Settings, the build is triggered according to the Cron expression, and depending on the settings, the pipeline is populated with the information from the Git repo, additional variables, and notifications when configured.

 {{site.data.callout.callout_tip}}
 **TIP**
 **TIP**
 To edit a Cron trigger after creating it, click the Edit icon.
 {{site.data.callout.end}}

 A Cron expression represents a set of time fields through five space-separated fields. You can also use predefined schedules or fixed interval scheduling in place of Cron expressions.

 ### Cron expression fields

 The table below describes the fields you can define in a Cron expression.

 {: .table .table-bordered .table-hover}
 Month        | Yes        | 1-12 or JAN-DEC | * / , -|
 Day of week  | Yes        | 0-6 or SUN-SAT  | * / , - ?|


 ### Special characters in Cron expressions

 The table below describes the purpose of the special characters in a Cron expression.

 {: .table .table-bordered .table-hover}
 |Special Character | Description |
 |----------   | ---------- |
 |**Asterisk** (`*`) | Indicates that the Cron expression will match for all values of the field.<br>Using an asterisk in the 5th field (month), would indicate every month.|
 |**Slash** (`/`) | Slashes are used to describe increments of ranges. <br>For example `3-59/15` in the 1st field (minutes) would indicate the 3rd minute of the hour and every 15 minutes thereafter. <br>The form `*\/...` is equivalent to the form `first-last/...`, that is, an increment over the largest possible range of the field. <br>The form `N/...` is accepted as meaning `N-MAX/...`, that is, starting at `N`, use the increment until the end of that specific range. It does not wrap around.|
 |**Comma** (`,`) | Commas are used to separate items of a list. For example, using `MON,WED,FRI` in the 5th field (day of week) would mean Mondays, Wednesdays and Fridays.|
 |**Hyphen** (`-`) | Hyphens are used to define ranges. For example, `9-17` would indicate every hour between 9am and 5pm inclusive.|
 |**Question mark** (`?`) | Question marks can be used instead of asterisks (`*`) for leaving either day-of-month or day-of-week blank.|

 |Special Character | Description |
 |----------   | ---------- |
 |**Asterisk** (`*`) | Indicates that the Cron expression will match for all values of the field.<br>Using an asterisk in the 5th field (month), would indicate every month.|
 |**Slash** (`/`) | Slashes describe increments of ranges. <br>For example `3-59/15` in the 1st field (minutes) would indicate the 3rd minute of the hour and every 15 minutes thereafter. <br>The form `*\/...` is equivalent to the form `first-last/...`, that is, an increment over the largest possible range of the field. <br>The form `N/...` is accepted as meaning `N-MAX/...`, that is, starting at `N`, use the increment until the end of that specific range. It does not wrap around.|
 |**Comma** (`,`) | Commas separate items in a list. For example, using `MON,WED,FRI` in the 5th field (day of week) would mean Mondays, Wednesdays, and Fridays.|
 |**Hyphen** (`-`) | Hyphens define ranges. For example, `9-17` would indicate every hour between 9am and 5pm inclusive.|
 |**Question mark** (`?`) | Question marks are instead of asterisks (`*`) to leave either day-of-month or day-of-week blank.|

 ### Predefined scheduling for Cron jobs

 You can use one of several predefined schedules instead of a Cron expression.
 The table below describes the predefined schedules supported.

 {: .table .table-bordered .table-hover}
 |Predefined schedule                  | Description| Equivalent to|
 |Predefined schedule                  | Description                  | Equivalent to|
 |-----                  | -----------                                | -------------|
 |@yearly (or @annually) | Run once a year, midnight, Jan. 1st        | 0 0 0 1 1 *|
 |@monthly               | Run once a month, midnight, first of month | 0 0 0 1 * *|
 |@weekly                | Run once a week, midnight on Sunday        | 0 0 0 * * 0|
 |@daily (or @midnight)  | Run once a day, midnight                   | 0 0 0 * * *|
 |@hourly                | Run once an hour, beginning of hour        | 0 0 * * * *|

 |@YEARLY (or @ANNUALLY) | Run once a year, midnight, Jan. 1st        | 0 0 0 1 1 *|
 |@MONTHLY               | Run once a month, midnight, first of month | 0 0 0 1 **|
 |@WEEKLY                | Run once a week, midnight on Sunday        | 0 0 0 ** 0|
 |@DAILY (or @MIDNIGHT)  | Run once a day, midnight                   | 0 0 0 ** *|
 |@HOURLY                | Run once an hour, beginning of hour        | 0 0 ** **|

 ### Fixed interval scheduling for Cron jobs

 You can also schedule a job to execute at fixed intervals by adding `@every <interval>`. The <interval> is a string that represents the desired frequency.

 You can also schedule a job to execute at fixed intervals by adding `@every <interval>`. The <interval> is a string that represents the desired frequency.
 For example, `@every 1h30m10s` would indicate a schedule that triggers every 1 hour, 30 minutes, 10 seconds.

 >**NOTE**
 The interval does not take the runtime of the job into account. For example, if a job takes three minutes to run, and it is scheduled to run every five minutes, it will have only two minutes of idle time between each run.

 ### Conditional triggers for Cron jobs

 Take a look at our Knowledge Base how-to: [Skip pipeline step if triggered by Cron job]({{site.baseurl}}/docs/kb/articles/skip-test-if-pipeline-is-triggered-with-cron/).

 ## Cron triggers with Codefresh CLI

 >**NOTE**
 This section is relevant only for legacy Cron triggers and will be deprecated.
 This section is relevant only for legacy Cron triggers and will be deprecated.

 You can also create and manage Cron triggers for pipelines via the [Codefresh CLI](https://cli.codefresh.io/){:target="\_blank"}.



 ### Create Cron trigger event via CLI

 Create a new `cron` trigger by defining a Cron expression and message.
 To learn about supported `cron` expression formats and aliases, see [Cron expression formats](#cron-expression-formats) in this article.
 The text message is passed to linked pipelines, whenever the specified `cron` timer is triggered.



 {% highlight yaml %}
 {% raw %}

 # create recurring event 'once in 20 minutes'
 codefresh create trigger-event --type cron --kind codefresh --value expression="0 */20 * * * *" --value message="hello-once-in-20-min"

 codefresh create trigger-event --type cron --kind codefresh --value expression="0 */20* ** *" --value message="hello-once-in-20-min"

 # on success trigger-event UID will be printed out
 Trigger event: "cron:codefresh:codefresh:0 */20 * * * *:hello-once-in-20-min:107e9db97062" was successfully created.

 Trigger event: "cron:codefresh:codefresh:0 */20* ** *:hello-once-in-20-min:107e9db97062" was successfully created.
 {% endraw %}
 {% endhighlight %}



 ### Set up pipeline trigger

 Now, lets create a new pipeline trigger, linking previously defined `cron` `trigger-event` to one or more Codefresh pipelines.

 Now, let's create a new pipeline trigger, linking previously defined `cron` `trigger-event` to one or more Codefresh pipelines.

 {% highlight yaml %}
 {% raw %}

 # create trigger, linking trigger-event UID to the pipeline UID
 codefresh create trigger "cron:codefresh:codefresh:0 */20 * * * *:hello-once-in-20-min:107e9db97062" 7a5622e4b1ad5ba0018a3c9c

 codefresh create trigger "cron:codefresh:codefresh:0 */20* ** *:hello-once-in-20-min:107e9db97062" 7a5622e4b1ad5ba0018a3c9c

 # create another trigger, linking the same trigger-event to another pipeline
 codefresh create trigger "cron:codefresh:codefresh:0 */20 * * * *:hello-once-in-20-min:107e9db97062" 4a5634e4b2cd6baf021a3c0a

 codefresh create trigger "cron:codefresh:codefresh:0 */20* ** *:hello-once-in-20-min:107e9db97062" 4a5634e4b2cd6baf021a3c0a
 {% endraw %}
 {% endhighlight %}


 The following variables are available to any Codefresh pipeline linked to a Cron trigger event:

 - `EVENT_MESSAGE`: Free-text message (specified during creation)
 - `EVENT_TIMESTAMP`: Event timestamp in RFC 3339 format
 * `EVENT_MESSAGE`: Free-text message (specified during creation)
 * `EVENT_TIMESTAMP`: Event timestamp in RFC 3339 format

 ## Related articles

 [Triggers in pipelines]({{site.baseurl}}/docs/pipelines/triggers/)
 [Cron trigger specifications]({{site.baseurl}}/docs/integrations/codefresh-api/#cron-triggers/)
 [Variables in pipelines]({{site.baseurl}}/docs/pipelines/variables/)
 [Creating pipelines]({{site.baseurl}}/docs/pipelines/pipelines/)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -16,16 +16,16 @@ Cron triggers offer a way to run Codefresh pipelines based on a specific time sc

		Integrate additional settings in the Cron trigger such as simulating a Git event to enrich pipelines with repository details, adding/customizing environment variables, and caching, volume reuse, and notification configurations for the build.

		By integrating these additional options, Cron triggers can initiate pipeline executions at the predefined time intervals and at the same time populate the pipeline with repo and branch information from the Git trigger, required environment variables, and specialized behavior, for the build.
		By integrating these additional options, Cron triggers can initiate pipeline executions at the predefined time intervals, and at the same time populate the pipeline with repo and branch information from the Git trigger, required environment variables, and specialized behavior for the build.

		Create and manage Cron triggers for pipelines through [Codefresh UI](#cron-triggers-in-codefresh-ui), as described in this article.
		For the specifications, see [Cron trigger specifications in pipelines]({{site.baseurl}}/docs/integrations/codefresh-api/#cron-triggers).

		>NOTE
		Cron triggers are created in the UTC timezone.

		## Legacy Cron triggers in Codefresh

		## Legacy Cron triggers in Codefresh
		If you see Cron triggers for your pipeline tagged with {::nomarkdown}<img src="../../../../images/icons/icon-warning.png" display=inline-block">{:/} tag, it indicates that you are using the legacy version.

		{% include image.html
Expand All		@@ -37,9 +37,11 @@ alt="Legacy Cron trigger in Codefresh UI"
		max-width="60%"
		%}

		Migrate legacy trigger
		* Click the Edit icon to view the trigger.
		* To migrate, click Convert.
		##### Migrate legacy Cron triggers

		1. Click the Edit icon to view the trigger.
		1. To migrate, click Convert.
		Codefresh migrates the legacy Cron trigger and displays a `Trigger updated successfully` message.

		{% include image.html
		lightbox="true"
Expand All		@@ -49,8 +51,9 @@ caption="Migrate legacy Cron trigger in Codefresh UI"
		alt="Migrate legacy Cron trigger in Codefresh UI"
		max-width="60%"
		%}
		Codefresh migrates the legacy Cron trigger and displays a Trigger updated successfully message.
		* Open the trigger displays the Settings tab with additional options.

		{:start="3"}
		1. Open the trigger displays the Settings tab with additional options.

		{% include image.html
		lightbox="true"
Expand All		@@ -61,30 +64,30 @@ alt="Cron trigger after migration with Settings tab"
		max-width="60%"
		%}


		## Cron triggers in Codefresh UI

		Create and manage Cron triggers for pipelines in the Codefresh UI.

		There are two parts to creating a Cron trigger in the UI:

		1. Defining the schedule for the trigger
		To learn about supported `cron` expression formats and aliases, see [Cron expression formats](#cron-expression-formats) in this article.
		1. (Optional) Selecting additional options:
		* Git trigger event to simulate when the Cron trigger timer is activated. The pipeline is populated with the information from the Git repo such as the repo URL, branch name, latest commit information, including the date and author of the commit.
		* Variables to populate for the build
		* Caching, volume reuse and notification behavior to override for the build

		* Git trigger event to simulate when the Cron trigger timer is activated. The pipeline is populated with the information from the Git repo such as the repo URL, branch name, latest commit information, including the date and author of the commit.
		* Variables to populate for the build.
		* Caching, volume reuse and notification behavior to override for the build.

		## Create a Cron trigger in UI

		## How to: Create a Cron trigger in UI
		Before you begin
		##### Before you begin

		Review:
		* [Git trigger settings]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/#git-trigger-settings)
		* [Git trigger settings]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/#git-trigger-settings)
		* [Working with Git triggers]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/#working-with-git-triggers)
		* [Cron expression formats](#cron-expression-formats)

		How to
		#####How to

		1. In the Codefresh UI, from the sidebar, select Pipelines.
		1. Select the pipeline to which to add the trigger, and then click the Workflow tab.
Expand All		@@ -97,7 +100,7 @@ file="/images/pipeline/triggers/add-trigger-dialog.png"
		url="/images/pipeline/triggers/add-trigger-dialog.png"
		caption="Select trigger type to add"
		alt="Select trigger type to add"
		max-width="60%"
		max-width="50%"
		%}

		{:start="5"}
Expand All		@@ -112,14 +115,14 @@ file="/images/pipeline/triggers/cron/cron-timer-tab.png"
		url="/images/pipeline/triggers/cron/cron-timer-tab.png"
		caption="Cron trigger: Cron Interval settings"
		alt="Cron trigger: Cron Interval settings"
		max-width="60%"
		max-width="50%"
		%}

		{:start="6"}
		1. Click Settings.
		1. Define the Git trigger simulation options:
		1. From the Simulate Trigger From drop-down list, select the type of Git trigger to simulate.
		The list displays all the Git triggers defined for the pipeline.
		The list displays all the Git triggers defined for the pipeline.
		1. From the Select Branch drop-down list, select the branch of the repository for this build.
		1. Expand Variables, and add or modify [environment variables]({{site.baseurl}}/docs/pipelines/variables/) for this build.
		1. Expand Advanced Options and select the overrides for this build. See [Advanced options]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/#advanced-settings-for-git-triggers).
Expand All		@@ -133,14 +136,13 @@ alt="Cron trigger: Cron trigger: Additional settings for Git event, variables, a
		max-width="60%"
		%}

		{:start="7"}
		1. To confirm click Done.
		* If you defined only the Timer settings, the build is triggered according to the Cron expression.
		* If you defined both the Timer and additional Settings, the build is triggered according to the Cron expression, and depending on the settings, the pipeline is populated with the information from the Git repo, additional variables, and notifications when configured.

		{:start="10"}
		1. To confirm click Done.
		* If you defined only the Timer settings, the build is triggered according to the Cron expression.
		* If you defined both the Timer and additional Settings, the build is triggered according to the Cron expression, and depending on the settings, the pipeline is populated with the information from the Git repo, additional variables, and notifications when configured.

		{{site.data.callout.callout_tip}}
		TIP
		TIP
		To edit a Cron trigger after creating it, click the Edit icon.
		{{site.data.callout.end}}

Expand All		@@ -149,6 +151,7 @@ To edit a Cron trigger after creating it, click the Edit icon.
		A Cron expression represents a set of time fields through five space-separated fields. You can also use predefined schedules or fixed interval scheduling in place of Cron expressions.

		### Cron expression fields

		The table below describes the fields you can define in a Cron expression.

		{: .table .table-bordered .table-hover}
Expand All		@@ -161,88 +164,86 @@ Day of month \| Yes \| 1-31 \| * / , - ?\|
		Month \| Yes \| 1-12 or JAN-DEC \| * / , -\|
		Day of week \| Yes \| 0-6 or SUN-SAT \| * / , - ?\|


		### Special characters in Cron expressions

		The table below describes the purpose of the special characters in a Cron expression.

		{: .table .table-bordered .table-hover}
		\|Special Character \| Description \|
		\|---------- \| ---------- \|
		\|Asterisk (`*`) \| Indicates that the Cron expression will match for all values of the field.<br>Using an asterisk in the 5th field (month), would indicate every month.\|
		\|Slash (`/`) \| Slashes are used to describe increments of ranges. <br>For example `3-59/15` in the 1st field (minutes) would indicate the 3rd minute of the hour and every 15 minutes thereafter. <br>The form `*\/...` is equivalent to the form `first-last/...`, that is, an increment over the largest possible range of the field. <br>The form `N/...` is accepted as meaning `N-MAX/...`, that is, starting at `N`, use the increment until the end of that specific range. It does not wrap around.\|
		\|Comma (`,`) \| Commas are used to separate items of a list. For example, using `MON,WED,FRI` in the 5th field (day of week) would mean Mondays, Wednesdays and Fridays.\|
		\|Hyphen (`-`) \| Hyphens are used to define ranges. For example, `9-17` would indicate every hour between 9am and 5pm inclusive.\|
		\|Question mark (`?`) \| Question marks can be used instead of asterisks (`*`) for leaving either day-of-month or day-of-week blank.\|

		\|Special Character \| Description \|
		\|---------- \| ---------- \|
		\|Asterisk (`*`) \| Indicates that the Cron expression will match for all values of the field.<br>Using an asterisk in the 5th field (month), would indicate every month.\|
		\|Slash (`/`) \| Slashes describe increments of ranges. <br>For example `3-59/15` in the 1st field (minutes) would indicate the 3rd minute of the hour and every 15 minutes thereafter. <br>The form `*\/...` is equivalent to the form `first-last/...`, that is, an increment over the largest possible range of the field. <br>The form `N/...` is accepted as meaning `N-MAX/...`, that is, starting at `N`, use the increment until the end of that specific range. It does not wrap around.\|
		\|Comma (`,`) \| Commas separate items in a list. For example, using `MON,WED,FRI` in the 5th field (day of week) would mean Mondays, Wednesdays, and Fridays.\|
		\|Hyphen (`-`) \| Hyphens define ranges. For example, `9-17` would indicate every hour between 9am and 5pm inclusive.\|
		\|Question mark (`?`) \| Question marks are instead of asterisks (`*`) to leave either day-of-month or day-of-week blank.\|

		### Predefined scheduling for Cron jobs

		You can use one of several predefined schedules instead of a Cron expression.
		The table below describes the predefined schedules supported.

		{: .table .table-bordered .table-hover}
		\|Predefined schedule \| Description\| Equivalent to\|
		\|Predefined schedule \| Description \| Equivalent to\|
		\|----- \| ----------- \| -------------\|
		\|@yearly (or @annually) \| Run once a year, midnight, Jan. 1st \| 0 0 0 1 1 *\|
		\|@monthly \| Run once a month, midnight, first of month \| 0 0 0 1 * *\|
		\|@weekly \| Run once a week, midnight on Sunday \| 0 0 0 * * 0\|
		\|@daily (or @midnight) \| Run once a day, midnight \| 0 0 0 * * *\|
		\|@hourly \| Run once an hour, beginning of hour \| 0 0 * * * *\|

		\|@YEARLY (or @ANNUALLY) \| Run once a year, midnight, Jan. 1st \| 0 0 0 1 1 *\|
		\|@MONTHLY \| Run once a month, midnight, first of month \| 0 0 0 1 **\|
		\|@WEEKLY \| Run once a week, midnight on Sunday \| 0 0 0 ** 0\|
		\|@DAILY (or @MIDNIGHT) \| Run once a day, midnight \| 0 0 0 ** *\|
		\|@HOURLY \| Run once an hour, beginning of hour \| 0 0 \|

		### Fixed interval scheduling for Cron jobs

		You can also schedule a job to execute at fixed intervals by adding `@every <interval>`. The <interval> is a string that represents the desired frequency.

		You can also schedule a job to execute at fixed intervals by adding `@every <interval>`. The <interval> is a string that represents the desired frequency.
		For example, `@every 1h30m10s` would indicate a schedule that triggers every 1 hour, 30 minutes, 10 seconds.

		>NOTE
		The interval does not take the runtime of the job into account. For example, if a job takes three minutes to run, and it is scheduled to run every five minutes, it will have only two minutes of idle time between each run.

		### Conditional triggers for Cron jobs

		Take a look at our Knowledge Base how-to: [Skip pipeline step if triggered by Cron job]({{site.baseurl}}/docs/kb/articles/skip-test-if-pipeline-is-triggered-with-cron/).

		## Cron triggers with Codefresh CLI

		>NOTE
		This section is relevant only for legacy Cron triggers and will be deprecated.
		This section is relevant only for legacy Cron triggers and will be deprecated.

		You can also create and manage Cron triggers for pipelines via the [Codefresh CLI](https://cli.codefresh.io/){:target="\_blank"}.



		### Create Cron trigger event via CLI

		Create a new `cron` trigger by defining a Cron expression and message.
		To learn about supported `cron` expression formats and aliases, see [Cron expression formats](#cron-expression-formats) in this article.
		The text message is passed to linked pipelines, whenever the specified `cron` timer is triggered.



		{% highlight yaml %}
		{% raw %}

		# create recurring event 'once in 20 minutes'
		codefresh create trigger-event --type cron --kind codefresh --value expression="0 /20 * * *" --value message="hello-once-in-20-min"

		codefresh create trigger-event --type cron --kind codefresh --value expression="0 /20 ** *" --value message="hello-once-in-20-min"

		# on success trigger-event UID will be printed out
		Trigger event: "cron:codefresh:codefresh:0 /20 * * *:hello-once-in-20-min:107e9db97062" was successfully created.

		Trigger event: "cron:codefresh:codefresh:0 /20 ** *:hello-once-in-20-min:107e9db97062" was successfully created.
		{% endraw %}
		{% endhighlight %}



		### Set up pipeline trigger

		Now, lets create a new pipeline trigger, linking previously defined `cron` `trigger-event` to one or more Codefresh pipelines.

		Now, let's create a new pipeline trigger, linking previously defined `cron` `trigger-event` to one or more Codefresh pipelines.

		{% highlight yaml %}
		{% raw %}

		# create trigger, linking trigger-event UID to the pipeline UID
		codefresh create trigger "cron:codefresh:codefresh:0 /20 * * *:hello-once-in-20-min:107e9db97062" 7a5622e4b1ad5ba0018a3c9c

		codefresh create trigger "cron:codefresh:codefresh:0 /20 ** *:hello-once-in-20-min:107e9db97062" 7a5622e4b1ad5ba0018a3c9c

		# create another trigger, linking the same trigger-event to another pipeline
		codefresh create trigger "cron:codefresh:codefresh:0 /20 * * *:hello-once-in-20-min:107e9db97062" 4a5634e4b2cd6baf021a3c0a

		codefresh create trigger "cron:codefresh:codefresh:0 /20 ** *:hello-once-in-20-min:107e9db97062" 4a5634e4b2cd6baf021a3c0a
		{% endraw %}
		{% endhighlight %}

Expand All		@@ -252,12 +253,12 @@ From now on, Codefresh will trigger a pipeline execution for two pipelines linke

		The following variables are available to any Codefresh pipeline linked to a Cron trigger event:

		- `EVENT_MESSAGE`: Free-text message (specified during creation)
		- `EVENT_TIMESTAMP`: Event timestamp in RFC 3339 format
		* `EVENT_MESSAGE`: Free-text message (specified during creation)
		* `EVENT_TIMESTAMP`: Event timestamp in RFC 3339 format

		## Related articles

		[Triggers in pipelines]({{site.baseurl}}/docs/pipelines/triggers/)
		[Cron trigger specifications]({{site.baseurl}}/docs/integrations/codefresh-api/#cron-triggers/)
		[Variables in pipelines]({{site.baseurl}}/docs/pipelines/variables/)
		[Creating pipelines]({{site.baseurl}}/docs/pipelines/pipelines/)