---
title: "Important: #111305 - Extbase persistence flushes caches via CacheFlusher"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:important-111305-1793474510"
source: "Changelog/15.0/Important-111305-ExtbasePersistenceFlushesCachesViaCacheFlusher.rst"
typo3-version: "15.0"
typo3-major: 15
type: "important"
issue: 111305
forge: "https://forge.typo3.org/issues/111305"
tags: ["Frontend", "PHP-API", "TypoScript", "ext:extbase"]
rendered: "2026-11-14T17:17:53+00:00"
---

# Important: #111305 - Extbase persistence flushes caches via CacheFlusher {#important-111305-1793474510}

See [forge#111305](https://forge.typo3.org/issues/111305)

## Description {#description}

Extbase persistence now flushes the caches of persisted records through
`\TYPO3\CMS\Core\Cache\Flush\CacheFlusher`, the same service
DataHandler uses, see [Feature: #111263 - Flush caches without DataHandler](https://docs.typo3.org/permalink/changelog:feature-111263-1793181135). The internal class
`\TYPO3\CMS\Extbase\Service\CacheService` has been removed. Code that
used it to flush page caches should use
`\TYPO3\CMS\Core\Cache\Flush\CacheFlusher` with
`CacheFlushDemand::forPageTagsByPageIds()` or
`CacheFlushDemand::forTags()` instead.

The caches are flushed once at the end of every
`PersistenceManager->persistAll()`, if the TypoScript setting
`config.tx_extbase.persistence.enableAutomaticCacheClearing` is
enabled, which is the default. Previously, the records were collected during
the request and flushed by the Extbase bootstrap after the plugin or module
had been rendered.

This changes how caches are flushed for records persisted by Extbase:

-   Caches are also flushed when `persistAll()` is called outside of an
    Extbase plugin or module, for example in console commands or scheduler
    tasks. Without a request, the setting falls back to its default.
-   Page TSconfig is evaluated like for records saved in the backend:
    `TCEMAIN.clearCache_disable`,
    `TCEMAIN.clearCache_pageSiblingChildren` and
    `TCEMAIN.clearCache_pageGrandParent` are respected, and
    `TCEMAIN.clearCacheCmd` flushes page ids and
    `cacheTag:<tag>` commands. The commands "pages" and "all"
    are never executed for records persisted by Extbase.
-   A persisted page record flushes the caches of the page, its siblings and
    its parent page instead of the caches of its parent page only.
-   The PSR-14 events
    `\TYPO3\CMS\Core\Cache\Event\BeforeRecordRelatedCachesAreFlushedEvent`,
    `\TYPO3\CMS\Core\Cache\Event\BeforeCacheFlushEvent` and
    `\TYPO3\CMS\Core\Cache\Event\AfterCacheFlushedEvent` are dispatched
    for records persisted by Extbase.

Records saved in the backend now also flush the cache tag
`<table>_pid_<pid>`, which the automatic frontend cache tagging of
Extbase repositories (feature toggle `frontend.cache.autoTagging`)
adds to lists of records of a storage page. A new record created in the
backend therefore evicts cached lists of its storage page as well.

A record moved to another page flushes the caches of its original page in
addition to the caches of its new page. This applies to records moved in
the backend and to objects whose "pid" is changed and persisted by Extbase,
which requires a TCA column "pid" of type "passthrough".
