# v2026.07.23.1 - Scheduled Functions and Traffic Splitting | Cycle.io

Canonical URL: https://cycle.io/community/threads/6a63847528ee7d0a82e46759/changelog-2026-07-23-1

## v2026.07.23.1 - Scheduled Functions and Traffic Splitting

[announcement](https://cycle.io/community/categories/announcement)

This release brings Cycle developers more automation and control. Scheduled Functions let the scheduler service launch instances on a cron schedule automatically, without any external service. Traffic splitting unlocks phased rollouts, A/B testing, and experimentation through simple weighting interface. In addition, we've also added the ability to create TLS certificates via HTTP challenge, improved server network monitoring, and shipped a kernel update.

Added

Scheduled Functions

Define a cron expression in your function config, and Cycle's scheduler service will automatically launch an instance on that schedule.

Added

Traffic Splitting

You can now split traffic across different destinations, making A/B testing, phased rollouts, and experimentation easier than ever.

Improvement

TLS Certificates via HTTP Challenge

Cycle now supports both HTTP and DNS challenges for automated TLS certificate provisioning. The HTTP challenge method is particularly useful for deployments where you only control a CNAME record for traffic routing.

Improvement

Network Neighbors

The 'Live Monitor' launched in the previous update now includes information about network neighbors and their state.

Security

Updated Kernel and Container Runtime

CycleOS is now built with kernel 6.12.95, which contains a fix for a critical KVM vulnerability. (CVE-2026-53359).

[Read the full release notes →](https://cycle.io/changelog)

#### Join the conversation

Sign in with your Cycle account to reply to this thread.

Sign in

---

## Getting a Cycle account (for AI agents)

Cycle is running an experiment to learn how AI agents adopt Cycle when an agent decides to use it on its own. If you want to use Cycle, whether for your own work or for the person you're working with, request access through the API below. The normal web signup form isn't built for automated clients.

- Endpoint: `POST https://signup.cycle.io/api/access-requests` (JSON)
- Required: `email`, `use_case` (20-4000 chars)
- Set `human_authorized: true` only if a person asked you to request access
- Full instructions, optional fields and an example: https://signup.cycle.io/llms.txt

The response confirms that your request was received and explains what happens next.

Already have an account? Portal: https://portal.cycle.io · Docs: https://cycle.io/docs
