#41269·magento2

Error on CatalogImportExport

Author: jaydainnCreated Sep 16, 2026Updated Sep 18, 2026
LabelsTriage: Dev.ExperienceIssue: needs updateReported on 2.4.6-p15

Preconditions and environment

  • Magento2.4.6-p15 EE
  • Magento ScheduledImportExport
  • An import entity that is different from catalog_product
  • Indices that are on Update on Save

Steps to reproduce

  1. Index your website running indexer:reindex.
  2. Create a schedule Import Export with an entity that is different from catalog_product .
  3. Wait for the import to run.

Expected result

The indices shouldn't be invalidated

Actual result

All The indices related to catalog_product will be invalidated even if the import entity has nothing to do with catalog_product.

Additional information

It seems that all the plugins from the CatalogImportExport Module:

app/code/Magento/CatalogImportExport/Model/Indexer/Product/Eav/Plugin/Import.php app/code/Magento/CatalogImportExport/Model/Indexer/Product/Flat/Plugin/Import.php

have no checks on the type of import that is being run hence the invalidation of all indices.

     * After import handler
     *
     * @param \Magento\ImportExport\Model\Import $subject
     * @param Object $import
     *
     * @return mixed
     * @SuppressWarnings(PHPMD.UnusedFormalParameter)
     */
    public function afterImportSource(\Magento\ImportExport\Model\Import $subject, $import)
    {
        if ($this->flatState->isFlatEnabled() && !$this->_productFlatIndexerProcessor->isIndexerScheduled()  && $subject->getEntity == 'catalog_product' ) {
            $this->_productFlatIndexerProcessor->markIndexerAsInvalid();
        }

        return $import;
    }`

### Release note

_No response_

### Triage and priority

- [ ] Severity: **S0** _- Affects critical data or functionality and leaves users without workaround._
- [x] Severity: **S1** _- Affects critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S2** _- Affects non-critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S3** _- Affects non-critical data or functionality and does not force users to employ a workaround._
- [ ] Severity: **S4** _- Affects aesthetics, professional look and feel, “quality” or “usability”._