Dynamic config with scheduled jobs

[nbialostosky]

Hi @mankut14 – thanks for the question, happy to help here!

At the moment the “Scheduled Workflow” feature, where you set schedules in your configuration file, doesn’t work with the dynamic config feature.

However, we just released “Scheduled Pipelines” which does work with the Dynamic Config setup:

Scheduled Pipelines Are Here

Update 6-Dec-2022: We previously announced that we will be sunsetting scheduled workflows at the end of this year. Since that announcement went live, we’ve been closely tracking your feedback and feature requests, and have decided to postpone the deprecation - no new timelines are set yet. We know that there is more work we need to do in order to improve the existing Scheduled Pipelines experience and also make migration easier for all. We will share updates as we have them. Thanks for your pati…

Essentially you’ll need to port over your previous schedules you had set in your configuration file to be “Scheduled Pipelines” via the API – you should then see your schedules continue.

Historically, here is some information around why it didn’t work and a previous workaround, though moving forward “Scheduled Pipelines” is the fix here:

[Workaround] Using scheduled workflows with Dynamic config

[Workaround] Using scheduled workflows with Dynamic config We recently released a feature called Dynamic config that unlocks a lot of options in using CircleCI. However, at the moment this feature is unable to be used in conjunction with scheduled workflows. The team is actively working on addressing this to allow for them to be used together. Since there isn’t a specific date of that release this guide is to help ensure both features can be used at the same time while that is being worked on. …

Hope the above helps!
-Nick