Overview

Scheduled workflows are not supported with Dynamic Configurations / Setup Workflows and scheduled workflows will be phased out to be replaced by scheduled pipelines as the primary method of scheduling work.

⚠  Scheduled Workflow Deprecation has been postponed to a later date  ⚠
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.

Scheduled Workflows vs. Scheduled Pipelines

There are many advantages to switching over to scheduled pipelines, some being:

• The ability to utilize dynamic configuration without a workaround
• Allowed use of auto-canceling
• The ability to modify the schedule without having to edit .circleci/config.yml

You can read about migrating from scheduled workflows to scheduled pipelines in Migrate scheduled workflows to scheduled pipelines.

Solution

At the moment you can utilize the following as a workaround to use scheduled workflows with dynamic config: Using scheduled workflows with Dynamic config.

Additional Resources:

• Scheduling a workflow
• Scheduled Pipelines
• Auto canceling