Merge branch 'main' into DOCSS-1930-unregistered-users

Author: rosieyohannan

docs/guides/modules/ROOT/examples/logic-statement-examples/when-in-workflows/and-equal-dynamic.yml

@@ -1,6 +1,6 @@
 workflows:
   nightly-run-workflow:
-# The "nightly-run-workflow" workflow only runs when the trigger is a scheduled pipeline AND the name of that trigger is "nightly_build"
+# The "nightly-run-workflow" workflow only runs when the trigger is scheduled AND the name of that trigger is "nightly_build"
     when: pipeline.trigger_source == "scheduled_pipeline" and pipeline.schedule.name == "nightly_build"
     jobs:
       - build

docs/guides/modules/ROOT/images/triggers/set-up-schedule-trigger.png

@@ -50,18 +50,17 @@
 *** xref:orchestrate:github-trigger-event-options.adoc[GitHub trigger event options]
 *** xref:orchestrate:gitlab-trigger-options.adoc[GitLab trigger options]
 *** xref:orchestrate:custom-webhooks.adoc[Custom webhooks]
-** Schedule
-*** xref:orchestrate:scheduled-pipelines.adoc[Scheduled pipelines]
+*** xref:orchestrate:schedule-triggers.adoc[Schedule triggers]
 ** How-to guides
 *** xref:orchestrate:orchestration-cookbook.adoc[Orchestration cookbook]
 *** xref:orchestrate:how-to-override-config.adoc[How to override config]
 *** xref:orchestrate:set-up-multiple-configuration-files-for-a-project.adoc[Set up multiple configuration files for a project]
 *** xref:orchestrate:notify-a-slack-channel-of-a-paused-workflow.adoc[Notify a Slack channel of a paused workflow]
 *** xref:orchestrate:using-branch-filters.adoc[Using branch filters]
 *** xref:orchestrate:selecting-a-workflow-to-run-using-pipeline-parameters.adoc[Select a workflow to run using pipeline parameters]
-*** xref:orchestrate:migrate-scheduled-workflows-to-scheduled-pipelines.adoc[Migrate scheduled workflows to scheduled pipelines]
-*** xref:orchestrate:schedule-pipelines-with-multiple-workflows.adoc[Schedule pipelines with multiple workflows]
-*** xref:orchestrate:set-a-nightly-scheduled-pipeline.adoc[Set a nightly scheduled pipeline]
+*** xref:orchestrate:migrate-scheduled-workflows-to-schedule-triggers.adoc[Migrate scheduled workflows to schedule triggers]
+*** xref:orchestrate:schedule-triggers-with-multiple-workflows.adoc[Schedule triggers with multiple workflows]
+*** xref:orchestrate:set-a-nightly-schedule-trigger.adoc[Set a nightly schedule trigger]
 *** xref:orchestrate:using-dynamic-configuration.adoc[Using dynamic configuration]
 *** xref:orchestrate:databases.adoc[Configure databases]
 *** xref:orchestrate:migrate-from-deploy-to-run.adoc[Migrate from deploy to run]

docs/guides/modules/ROOT/nav.adoc

@@ -1,3 +1,5 @@
 . In the link:https://app.circleci.com[CircleCI web app], select your org from the org cards on your user homepage.
 . Select **Projects** from the sidebar and locate your project from the list. You can use the search to help.
 . Select the ellipsis image:guides:ROOT:icons/more.svg[more icon, role="no-border"] next to your project and select **Project Settings**.
++
+TIP: You can also access project settings from each project overview page using the btn:[Settings] button.

docs/guides/modules/ROOT/partials/app-navigation/steps-to-project-settings.adoc

@@ -0,0 +1,41 @@
+[#can-i-migrate-existing-scheduled-workflows]
+=== Can I migrate existing scheduled workflows to schedule triggers?
+
+Yes, visit the xref:guides:orchestrate:migrate-scheduled-workflows-to-schedule-triggers.adoc[Schedule triggers migration] guide for more information.
+
+[#find-schedules-that-i-have-created]
+=== How do I find the schedules that I have created?
+
+As schedule triggers are stored directly in CircleCI, there is a UUID associated with each schedule. You can view schedules that you have created on the **Triggers** page of the project settings. You can also list all the schedules under a single project:
+
+```shell
+curl --location --request GET "https://circleci.com/api/v2/project/<project-slug>/schedule" \
+--header "circle-token: <PERSONAL_API_KEY>"
+```
+
+Refer to the xref:guides:toolkit:api-developers-guide.adoc#getting-started-with-the-api[Getting started with the API] section of the API Developer's Guide for more guidance on making requests.
+
+=== What time zone is used for schedule triggers?
+
+Coordinated Universal Time (UTC) is the time zone in which schedules are interpreted.
+
+[#pipelines-scheduled-to-run-specific-time-of-day]
+=== Can pipelines be scheduled to run at a specific time of day?
+
+Yes, you can set up xref:guides:orchestrate:schedule-triggers.adoc[schedule triggers] through the xref:guides:orchestrate:schedule-triggers.adoc#get-started-with-schedule-triggers[CircleCI web app], or with xref:guides:orchestrate:schedule-triggers.adoc#use-the-api[CircleCI API v2].
+
+If you are currently using xref:guides:orchestrate:workflows.adoc#scheduling-a-workflow[Scheduled workflows], see the xref:guides:orchestrate:migrate-scheduled-workflows-to-schedule-triggers.adoc[Migration guide] to update your scheduled workflows to schedule triggers.
+
+=== Are schedule triggers guaranteed to run at precisely the time scheduled?
+
+CircleCI provides no guarantees about precision. A random delay of up to 10 minutes is applied to the scheduled time (this delay can be up to one hour for schedule triggers created before September 29 2025). After the first run, the delay will be constant for all subsequent runs.
+
+=== Why did my schedule trigger run later than expected?
+
+Pipelines triggered via schedule are not guaranteed to run at exactly the specified time. For example, when you express the schedule as 1 per-hour for 08:00 UTC, the schedule trigger will run once within the 08:00 to 09:00 UTC window. Note that it means that it is unlikely to run at 08:00 UTC exactly.
+
+However, subsequent runs of the schedule trigger will always be run on the same time as its previous run. In other words, if a previous schedule trigger ran at 08:11 UTC, the next runs should also be at 08:11 UTC.
+
+=== Why can I not add a schedule trigger to my pipeline?
+
+Only GitHub OAuth, GitHub App and Bitbucket Cloud pipelines support schedule triggers. GitLab and Bitbucket Data Center pipelines do not support schedule triggers. If you set up a schedule trigger through menu:Project Settings[Triggers] and do not see your pipeline in the "Pipeline to run" menu, check your pipeline type is supported .

docs/guides/modules/ROOT/partials/faq/schedule-trigger-faq-snip.adoc

@@ -120,15 +120,15 @@ d| [.nowrap]#GitHub App# +
 d| [.nowrap]#GitHub OAuth# +
 [.nowrap]#Bitbucket Cloud#
 | String
-| The name of the schedule if it is a scheduled pipeline. Value will be empty string if the pipeline is triggered by other sources.
+| The name of the schedule trigger if the pipeline was triggered via schedule. The value will be empty string if the pipeline is triggered by other sources.
 | [.circle-green]#**Yes**#
 | [.circle-green]#**Yes**#
 
 | `pipeline.schedule.id`
 d| [.nowrap]#GitHub OAuth# +
 [.nowrap]#Bitbucket Cloud#
 | String
-| The unique id of the schedule if it is a scheduled pipeline. Value will be empty string if the pipeline is triggered by other sources.
+| The unique ID of the schedule if the pipeline was triggered via schedule trigger. Value will be empty string if the pipeline is triggered by other sources.
 | [.circle-green]#**Yes**#
 | [.circle-green]#**Yes**#
 

docs/guides/modules/ROOT/partials/faq/scheduled-pipelines-faq-snip.adoc

@@ -0,0 +1,88 @@
+[tabs]
+====
+GitHub App::
++
+--
+include::ROOT:partial$app-navigation/steps-to-project-settings.adoc[]
+
+. Select **Project Setup** in the sidebar.
+Locate your pipeline and select btn:[Schedule +].
+. Complete the schedule trigger form:
++
+image::guides:ROOT:triggers/set-up-schedule-trigger.png[Schedule triggers web app form]
+** Give your trigger a descriptive name.
+** Select a branch to tell CircleCI which code to checkout and where to find your config file.
+** Under Pipeline attribution, select the actor to initiate the trigger. You can choose yourself, one of your team, or the scheduling system if you want the trigger to be independent from individual users. If your project requires the use of environment variables stored in restricted contexts, you should assign someone who has access to those contexts.
+** Enter any pipeline parameters that you would like to set when triggering the pipeline. If you enter any new pipeline parameters make sure to also add them to your config file. You can select btn:[Populate from config] to automatically populate the parameters fields from your config file.
+** Select a trigger frequency and repeat options.
++
+[options="header",cols="1,2"]
+|===
+|Field |Options
+
+|Repeats
+|Weekly, Monthly
+
+|Days of the week
+| Radio buttons for each or select all
+
+|Months
+| Radio buttons for each or select all
+
+|Start time (UTC)
+| Radio buttons for each hour or select all
+
+| Times per hour
+a|* 1 (once per hour)
+* 2 (every 30 minutes)
+* 3 (every 20 minutes)
+* 4 (every 15 minutes)
+* 5 (every 12 minutes)
+* 6 (every 10 minutes)
+* 7 (every 8.6 minutes)
+* 8 (every 7.5 minutes)
+* 9 (every 6.7 minutes)
+* 10 (every 6 minutes)
+* 11 (every 5.5 minutes)
+* 12 (every 5 minutes)
+|===
+
+. Enable the trigger and select btn:[Save].
+--
+GitHub OAuth::
++
+--
+include::ROOT:partial$app-navigation/steps-to-project-settings.adoc[]
+
+. Select **Triggers** in the sidebar.
+. Select btn:[Add Trigger].
++
+image::guides:ROOT:pipelines-scheduled-trigger-form.png[Schedule triggers web app form]
+** Give your trigger a descriptive name.
+** Enter an optional trigger description.
+** Select the pipeline to run.
+** Select a release frequencies (weekly/monthly, which days/months/time etc.).
+** Enter a branch or tag name to determine when to trigger the pipeline.
+** Optionally, enter pipeline parameters. If you declare pipeline parameters in the form, you need to make sure they are configured in your project's `.circleci/config.yml`. See the xref:guides:orchestrate:pipeline-variables.adoc#pipeline-parameters-in-configuration[Pipeline values and parameters] page for more information.
+** Select an actor to initiate the trigger.
+. Define the new schedule by filling out the form, then select **Save Trigger**.
+--
+Bitbucket Cloud::
++
+--
+include::ROOT:partial$app-navigation/steps-to-project-settings.adoc[]
+
+. Select **Triggers** in the sidebar.
+. Select btn:[Add Trigger].
++
+image::guides:ROOT:pipelines-scheduled-trigger-form.png[Schedule triggers web app form]
+** Give your trigger a descriptive name.
+** Enter an optional trigger description.
+** Select the pipeline to run.
+** Select a release frequencies (weekly/monthly, which days/months/time etc.).
+** Enter a branch or tag name to determine when to trigger the pipeline.
+** Optionally, enter pipeline parameters. If you declare pipeline parameters in the form, you need to make sure they are configured in your project's `.circleci/config.yml`. See the xref:guides:orchestrate:pipeline-variables.adoc#pipeline-parameters-in-configuration[Pipeline values and parameters] page for more information.
+** Select an actor to initiate the trigger.
+. Define the new schedule by filling out the form, then select **Save Trigger**.
+--
+====

docs/guides/modules/ROOT/partials/pipelines-and-triggers/pipeline-values.adoc

@@ -18,8 +18,8 @@ config file .circleci/sample-filename.yml could not be located on branch sample-
 
 If your scheduled pipeline is not running, verify the following things:
 
-- Is the actor who is set for the scheduled pipelines still part of the organization? You can find this setting is under **Attribution** in the **Triggers** section of the web app.
-- Is the branch set for the schedule deleted?
+- Is the actor who is set for the schedule trigger still part of the organization? You can find this setting in the *Pipeline attribution* section for your trigger in the CircleCI web app.
+- Does the branch set for the trigger still exist?
 - Is your VCS organization using SAML protection? SAML tokens expire often, which can cause requests to fail.
 
 [#jobs-not-running-when-push-commits]