With Passthrough Rollouts, if a rollout or schedule hasn’t been hit for a given user, they will pass through and be evaluated against the subsequent rules. They will not be “held” on the first rule and can be served the targeting of subsequent rules. This allows you to manage complex schedules and variation changes for the same audience more easily.

Currently this functionality is opt-in, you can turn it on today by enabling it on your project’s settings pages.

On July 17, 2024, we will make Passthrough Rollouts the default functionality for all schedules and rollouts. If your team is actively using the Scheduled Rollouts functionality for Targeting Rules, this change may affect how Targeting Rules behave for your Features.

For our server-side SDKs, we recommend upgrading your SDK before July 17, 2024, and before turning Passthrough Rollouts on. If you do not update your SDK, the Targeting Rule behavior will remain the same, but client-side SDKs will use the passthrough targeting logic.

Client-side SDK users can opt-in whenever you'd like without an SDK update and start using the new targeting rule behaviour immediately.

Here is a link to our docs for more info on Passthrough Rollouts & the required server-side SDK versions!

DevCycle changelog

Passthrough Rollouts: Ability to "pass through" a Targeting Rule