How to Manually Trigger a Scheduled Pipeline

Why Trigger a Scheduled Pipeline Manually?

Sometimes you may need to run a scheduled pipeline outside the scope of your scheduled time in order to debug or test that a workflow in a pipeline is working as expected. While CircleCI does not have an out-of-the-box solution for this, the Support team has come up with a workaround!


Triggering via the API:

The best way to achieve this would be to duplicate the desired workflow in your config, then add a condition to only run the job based on an API trigger:

equal: [ api, << pipeline.trigger_source >> ]
<specify jobs here>


You can then trigger the pipeline using the following API endpoint:

This would allow you to control when the pipeline is triggered and make sure that no jobs are duplicated unnecessarily.


Additional Notes:

It should be noted that the Scheduled Workflow functionality is being deprecated in the future. We have documentation on how to migrate to Scheduled Pipelines here on our documentation site:

If you have any additional questions related to this topic, please feel free to reach out to our Support team!

Was this article helpful?
0 out of 1 found this helpful



Article is closed for comments.