The`triggers` field is an array of objects that hold[Git trigger information]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/) with the following fields.

The`triggers` field is an array of objects that hold[Git trigger information]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/).

{: .table .table-bordered .table-hover}

| Field name| Parent field| Type| Value|

The`crontriggers` field is an array of objects that hold[Cron trigger information]({{site.baseurl}}/docs/pipelines/triggers/cron-triggers/) with the following fields.

The`cronTriggers` field is an array of objects that hold[Cron trigger information]({{site.baseurl}}/docs/pipelines/triggers/cron-triggers/).

{: .table .table-bordered .table-hover}

| Field name| Parent field| Type| Value|

| --------------| ----------------------------|-------------------------| -------------------------|

|`name`|`cronTriggers`| string| The user-defined name for the Cron trigger.|

|`message`|`cronTriggers`| string|The free-text message to be sent as an additional event payload every time the Cronjob isexecuted. For example,`Successful ingress-less`|

|`expression`|`cronTriggers`| string|The Cron expression that defines the time and frequency of the Cronjob.For example,`0 3 * * 1-5` triggers the pipeline at`3:00 AM every weekday (Monday to Friday)`.|

|`disabled`|`cronTriggers`| boolean| Determines if the Cron trigger isactivated. Whenset to`true`, triggerisnot activated. What is thedefault?|

|`gitTriggerId`|`cronTriggers`| string| The ID of the Git trigger toactivate. From where do they git the trigger Id?|

|`branch`|`cronTriggers`| string| The branch of the repo for which to simulate the Git trigger. For??|

|`variables`|`cronTriggers`| array| The environment variables to populate for the pipeline???|

|`options`|`cronTriggers`| string| ???|

|`message`|`cronTriggers`| string|The free-text message to be sent as an additional event payload every time the Crontrigger isactivaed. For example,`Successful ingress tests`|

|`expression`|`cronTriggers`| string|The Cron expression that defines the time and frequency of the Crontrigger.<br>For example,`0 3 * * 1-5`triggers the pipeline at_3:00 AM every weekday (Monday to Friday)_.|

|`disabled`|`cronTriggers`| boolean| Determines if the Cron trigger isenabled for activation. <br>By default,set to`false` meaning that itisalways enabled. <br>To disable thetrigger, set to`true`.|

|`gitTriggerId`|`cronTriggers`| string| The ID of the Git trigger tosimulate for the pipeline, retrieved from thepipeline for which it is defined.<br>To simulate a Gittrigger, the pipeline must have at least one Git trigger defined for it.<br>See[Git triggers](#git-triggers) in this article.|

|`branch`|`cronTriggers`| string|Valid only when a Git trigger is simulated.<br>The branch of the repo for which to simulate the Git trigger and is automatically populated from the Git trigger ID.|

|`variables`|`cronTriggers`| array|Valid only when a Git trigger is simulated.<br>The environment variables to populate for the pipeline when the Cron trigger is activated.|

| `options` | `cronTriggers` | array | Valid only when a Git trigger is simulated.<br>The behavior override options to implement for the current build. By default all overrides are set to `false`, meaning that the build inherits the default behavior set for the pipeline at the account level. <br>Can be any of the following:<br>{::nomarkdown}<ul><li><code class="highlighter-rouge">noCfCache</code>: When set to <code class="highlighter-rouge">true</code>, ignores Docker engine cache for build. See <a href="https://codefresh.io/docs/docs/kb/articles/disabling-codefresh-caching-mechanisms">Docker engine cache</a></li><li><code class="highlighter-rouge">noCache</code>: When set to <code class="highlighter-rouge">true</code>, ignores the last build's cache. Selecting this option may slow down your build.<br>See <a href="https://codefresh.io/docs/docs/kb/articles/disabling-codefresh-caching-mechanisms">Last build cache</a>.</li><li><code class="highlighter-rouge">resetVolume</code>: When set to <code class="highlighter-rouge">true</code>, resets the pipeline volume, useful for troubleshooting a build that hangs on the first step.<br> See <a href="https://codefresh.io/docs/docs/kb/articles/restoring-data-from-pre-existing-image-hangs-on/" target="_blank">Hangs on restoring data from pre-existing image</a>.</li><li><code class="highlighter-rouge">enableNotifications</code>: When set to <code class="highlighter-rouge">true</code>, sends Slack notifications, in addition to status updates to your Git provider.<br>See <a href="https://codefresh.io/docs/docs/integrations/notifications/slack-integration/" target="_blank">Slack notifications</a>.</li></ul>{:/}|

example

{% highlight yaml %}

{% raw %}

...

cronTriggers:

- name:

type: cron,

message: "Successfull ingress tests"

expression: "0 0/1 * 1/1 * *

gitTriggerId: 64905de8589da959de81d31d

branch: main

variables:[]

options:

noCfCache: false

noCache: false

resetVolume: false

enableNotifications: true

disabled: true

event: cron:codefresh:0 0/1 * 1/1 **:tests:ecef63b9ed20

verified: true

status: verified

id: 64ddd8b04fdbcc74cc74fe80

...

{% endraw %}

{% endhighlight %}

%}

Legacy Cron triggers in the UI are marked as ???. You can edit the trigger and update it

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

There are two parts to creating a Cron trigger:

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, visit[this page](https://github.com/codefresh-io/cronus/blob/master/docs/expression.md){:target="\_blank"}.

1. Optional; defining the Git trigger event to simulate when the Cron trigger timer is activated.

The Git trigger works the same way it does for the

1. (Optional) selecting the Git trigger event to simulate when the Cron trigger timer is activated.

Simulating a Git trigger has the same impact

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.

1. From the**Select Branch** drop-down list, select the branch of the repository for this build.

The branches corresponding to the repo for the selected Git trigger are displayed.

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).

Now you can Recurring pipeline executions are triggered according to the defined settings.

* If you defined only the Timer settings, the build is triggered according to the Cron expression.

* If you defined both the Timer and Git Settings, the build is triggered according to the Cron expressionwhentheGit event is triggered atthe repo branch.

* If you defined both the Timer and Git Settings, the build is triggered according to the Cron expressionand populated withtheinformation from the Git repo such astheGitrepoURL,branch name, latest commit information, including the date and author of the commit.

???

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

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

You first create the Cron trigger and then set up a

Create a new`cron` triggerthrough a Cron expression and message.

Create a new`cron` triggerby defining a Cron expression and message.

To learn about supported`cron` expression formats and aliases, visit[this page](https://github.com/codefresh-io/cronus/blob/master/docs/expression.md){:target="\_blank"}.

The text message is passed to linked pipelines, whenever the specified`cron` timer is triggered.