---
title: "Scheduler as Code"
manual: "Scheduler as Code"
version: "main"
permalink: "https://docs.typo3.org/permalink/maikschneider/scheduler-as-code:start@main"
source: "Index.rst"
start: true
rendered: "2026-10-06T08:46:59+00:00"
---

# Scheduler as Code {#start}

-   *Extension key:* scheduler_as_code
-   *Package name:* maikschneider/scheduler-as-code
-   *Version:* release
-   *Language:* en
-   *Author:* Maik Schneider & Contributors
-   *License:*

    This document is published under the
    [Open Publication License](https://www.opencontent.org/openpub/).

-   *Rendered:* today

---

Scheduler as Code keeps TYPO3 scheduler tasks in YAML files under version control.
Tasks are imported into the database automatically, so every environment runs the
tasks the repository describes.

---

**[Introduction](https://docs.typo3.org/permalink/maikschneider/scheduler-as-code:introduction@main)**

What the extension does, and how it differs from the scheduler on its own.

**[Installation](https://docs.typo3.org/permalink/maikschneider/scheduler-as-code:installation@main)**

Install the extension with Composer and set up the database.

**[Usage](https://docs.typo3.org/permalink/maikschneider/scheduler-as-code:usage@main)**

Export existing tasks, edit task files, and read the badges in the
Scheduler module.

**[Task files](https://docs.typo3.org/permalink/maikschneider/scheduler-as-code:task-files@main)**

Reference of every key in a task file, including task parameters.

**[Site sets](https://docs.typo3.org/permalink/maikschneider/scheduler-as-code:site-sets@main)**

Ship tasks with an extension and activate them per site.

**[Deployment](https://docs.typo3.org/permalink/maikschneider/scheduler-as-code:deployment@main)**

When the import runs, and what a deployment has to do.

**[Known problems](https://docs.typo3.org/permalink/maikschneider/scheduler-as-code:known-problems@main)**

Troubleshooting failed imports and current limitations.