title:"How To: Skip step if pipeline triggered with Cron"

description:

group:kb

sub-group:articles

toc:true

kb:false

ht:true

common:false

categories:[Pipelines]

support-reviewed:2023-12-12 MB

You have a build with multiple triggers and you need to skip a certain step if the pipeline was launched using a Cron trigger.

In the**Message** field of the Cron trigger configuration settings, set a message, for example, "using cron".

Use the`EVENT_MESSAGE` variable in your pipeline steps with a condition as in the following example:

{% raw %}

{% endraw %}

The condition ensures that specific steps execute only when the pipeline is triggered by Cron,_and_ if the Cron job message differs from the one defined in the Message field (`using cron` in our example).

[Triggers in pipelines]({{site.baseurl}}/docs/pipelines/triggers/)

[Cron trigger event variables]({{site.baseurl}}/docs/pipelines/triggers/cron-triggers/#cron-event-payload)

[Conditional execution of steps]({{site.baseurl}}/docs/pipelines/conditional-execution-of-steps/)

[Freestyle step]({{site.baseurl}}/docs/pipelines/steps/freestyle/)

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, volumeresuse and notification behavior to override for the build

* Caching, volumereuse and notification behavior to override for the build

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.

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