# How to handle rate limiting by external systems with Scheduled Triggers?

**URL:** <https://discuss.circleci.com/t/how-to-handle-rate-limiting-by-external-systems-with-scheduled-triggers/49658>\
**Category:** Build Environment\
**Created:** [October 24, 2023, 6:21pm UTC](https://discuss.circleci.com/t/how-to-handle-rate-limiting-by-external-systems-with-scheduled-triggers/49658 "2023-10-24T18:21:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ddl-pjohnson](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@ddl-pjohnson](https://discuss.circleci.com/u/ddl-pjohnson)\
**Post date:** [October 24, 2023, 6:21pm UTC](https://discuss.circleci.com/t/how-to-handle-rate-limiting-by-external-systems-with-scheduled-triggers/49658/1 "2023-10-24T18:21:13Z")

</div>

Hi, we need to run a nightly security scanning job on many repos through scheduled triggers. We’re concerned that we will suffer from rate limiting by external systems if we schedule all of these to run at once. It looks like scheduled triggers only support hourly start times, so how do we ensure we don’t get rate limited? (Or is the start time already randomized across the hour?)

---

<div class="post-metadata">

**Author:** ![rit1010](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/rit1010/32/34738_2.png) [@rit1010](https://discuss.circleci.com/u/rit1010)\
**Post date:** [October 24, 2023, 9:46pm UTC](https://discuss.circleci.com/t/how-to-handle-rate-limiting-by-external-systems-with-scheduled-triggers/49658/2 "2023-10-24T21:46:46Z")

</div>

One answer to the limitations of the current Scheduled Triggers solution, if you have your own infrastructure is that you could start piplines via the API using a Scheduling tool that you run locally.

The following write-up includes a curl example that uses the API to start a project pipeline.

```
 https://therightstuff.medium.com/creating-manual-circleci-workflow-triggers-2d4871f820f2

```

I know this is not a great answer, but we are still waiting to hear what circleci has planned for scheduled triggers as they were designed to replace the older scheduled workflows feature, but they have admitted that additional work is required to match the features of the original solution.

Sadly the old solution is now only available to BitBucket users, but if you are such a user you can find some basic details here

> **[Migrate scheduled workflows to scheduled pipelines - CircleCI](https://circleci.com/docs/migrate-scheduled-workflows-to-scheduled-pipelines/)**
>
> Migrate scheduled workflows to scheduled pipelines

---

<div class="post-metadata">

**Author:** ![ddl-pjohnson](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@ddl-pjohnson](https://discuss.circleci.com/u/ddl-pjohnson)\
**Post date:** [October 24, 2023, 10:02pm UTC](https://discuss.circleci.com/t/how-to-handle-rate-limiting-by-external-systems-with-scheduled-triggers/49658/3 "2023-10-24T22:02:25Z")

</div>

Thanks, figured that was the case, I think we’re alright for now, but down the line we might end up using github actions to kick off Circle.