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

# Known problems {#known-problems}

## A task file is not imported {#known-problems-troubleshooting}

Check the TYPO3 log first, see [Logging](https://docs.typo3.org/permalink/maikschneider/scheduler-as-code:deployment-logging@main).

-   **The file is not valid YAML, or misses `type` or `execution`**

    The import stops until the file changes. Fix the file; the next request
    imports it.

-   **The task type does not exist**

    For example, the console command belongs to an uninstalled extension, or the
    command is not schedulable. Only this task is skipped; all others are
    imported.

-   **The database schema is not up to date**

    Run `vendor/bin/typo3 extension:setup`. The import is retried on every
    boot until it succeeds.

-   **A site set's tasks are missing**

    The set has to be used by a site, see [Which tasks are imported](https://docs.typo3.org/permalink/maikschneider/scheduler-as-code:site-sets-activation@main). After
    editing a site's `config.yaml` by hand, flush the caches.

## Limitations {#known-problems-limitations}

-   Parameters of task classes differ between TYPO3 13 and 14, see
    [Task classes](https://docs.typo3.org/permalink/maikschneider/scheduler-as-code:task-parameters-classes@main). A file written for one version may need
    adjusting after an upgrade. Console command tasks are not affected.
-   The extension is in alpha state. The file format may still change.