---
title: "Scheduling"
id: "1813"
type: "page"
slug: "scheduling"
published_at: "2026-09-20T22:08:59+00:00"
modified_at: "2026-09-21T01:36:28+00:00"
url: "https://xedant.com/agents/telegram/docs/scheduling"
markdown_url: "https://xedant.com/agents/telegram/docs/scheduling.md"
excerpt: "The Scheduling section is the channel’s weekly publishing plan: slots, a “time × day of…"
---

# Scheduling

[https://xedant.com/agents/telegram/docs/scheduling.md](https://xedant.com/agents/telegram/docs/scheduling.md)

The Scheduling section is the channel’s weekly publishing plan: slots, a “time × day of week” grid, estimated dates and auto-publishing. It turns “I really should post something” into a predictable flow of content.

## Slots — the channel’s weekly plan

A slot is a set of days of the week (Mon–Sun) with one or several times: for example, Mon/Wed/Fri at 10:00 and 18:00. A slot has a name, a description, a color and an icon, and can be turned off and on. You do not have to invent a name — it is suggested from the chosen days and times.

## The schedule grid

The schedule is drawn as a grid: rows are times, columns are days of the week. A filled cell shows its slot by color; an empty one invites you to create a slot for exactly that day and time — they are pre-filled for you. Clicking a cell is creating; the separate “Add slot” button creates a slot with Monday by default. Invalid times are dropped quietly, and a slot without a day or without a time will not save — the application explains what is missing.

## The time zone

Slot times are set in the channel’s time zone (UTC by default, chosen in the channel settings) — and the slot editor shows which zone you are entering the times in. Daylight-saving transitions are accounted for when computing occurrences; if the time zone cannot be resolved, the computation safely falls back to UTC.

## The publish date computes itself

For an item placed in a slot, the publish date is derived from its position in the slot’s queue: the first takes the slot’s nearest occurrence, the next one the one after that, and so on. The computation looks 60 days ahead. The date is not stored anywhere, so reordering the queue immediately moves all the dates — nothing needs to be recalculated by hand.

## Suggestions when planning

- **“Next scheduled slot”** — the earliest upcoming occurrence of any enabled slot of the channel;
- **“Next empty slot”** — the nearest occurrence of a slot that holds no scheduled content yet. If no free occurrence is found within 30 days ahead, the application tells you so honestly.

## Auto-publishing

When a slot’s moment arrives, the first scheduled item publishes itself — provided the channel has auto-publishing enabled. One post per occurrence, with no catch-up: if the server was down at the slot’s moment, the missed occurrence is not published, and the next slot takes the next post. If auto-publishing is off, slots never publish anything on their own — manual publishing keeps working as usual.

## What is next

How content gets into slots is in the [Content Queue](/agents/telegram/docs/queue)
 section, and how publishing itself works in [Publishing](/agents/telegram/docs/publishing)
.

[← Back to the documentation index](/agents/telegram/docs)