---
title: "Bandwidth schedules"
description: "Schedule Flux bandwidth changes: a one-shot change at a set date and time, or a recurring business-hours profile, including how schedules work with Auto-Flux."
---

> Documentation Index
> Fetch the complete documentation index at: https://support.vigilis.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Bandwidth schedules

The Network section (branded "Flux" in some places) is for admins and needs the Network add-on on your plan. Depending on your plan and role you may not see it in the sidebar. If you think it should be part of your plan, ask your provider.

`/network/schedules` lets you set bandwidth changes to happen automatically on a schedule, without anyone having to submit a manual change on the day.

## Single change (one-shot)

A one-shot schedule makes a single change at a specific time. Its fields are a **name**, one or more **connections**, a **target bandwidth**, and a **date and time**. Use it for a known event, a cutover, or a temporary need.

## Business-hours profile (recurring)

A business-hours profile repeats weekly. Its fields are a **name**, one or more **connections**, a **business-hours speed** (a fixed tier or "Auto-Flux"), an **after-hours speed**, a **start and end time**, and the **days of the week** it runs (Monday through Friday by default).

## Using a schedule with Auto-Flux

To combine [Auto-Flux](/network/auto-flux/) with a schedule on the same circuit, use a business-hours profile and set the **business-hours speed to "Auto-Flux."** Auto-Flux then runs during business hours, following real traffic, and the profile pauses it after hours at your fixed after-hours speed. That way it does not spend change budget overnight.

Do not instead set a **fixed** business-hours speed and leave Auto-Flux turned on for the same circuit. The schedule and Auto-Flux would then contend over the speed, each moving it a different direction. Pick one approach per circuit: either a fixed schedule, or Auto-Flux driving the business-hours side.

## Schedules vs. Auto-Flux

Schedules act on the clock; Auto-Flux acts on real, measured usage. Use a schedule when you already know the pattern you want, and Auto-Flux when you would rather have bandwidth follow actual traffic. Every scheduled change is recorded alongside manual and automatic ones in the Activity log.

## Related

- [Circuit connections](/network/circuit-connections/) for the circuit inventory, manual changes, and the Activity log.
- [Auto-Flux](/network/auto-flux/) for automatic right-sizing based on measured usage.
- [Connecting usage data](/network/setting-up-network/) for the one-time data setup.

## Common questions

**How do I run Auto-Flux during the day but leave bandwidth fixed overnight?**

Create a business-hours profile and set the business-hours speed to Auto-Flux, with a fixed after-hours speed. Auto-Flux then scales during business hours and pauses after hours, so it does not spend change budget overnight.

**Which days does a business-hours profile run by default?**

Monday through Friday. You can change the selected days, along with the start and end times, when you create or edit the profile.

Source: https://support.vigilis.io/network/bandwidth-schedules/index.mdx
