Indexing Error Class Magento\Catalog\Model\Indexer\Category\Product\Action\Full\Interceptor does not exist Magento Version 2.3.5

Indexing Error Class Magento\Catalog\Model\Indexer\Category\Product\Action\Full\Interceptor does not exist Magento Version 2.3.5

August 11, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Indexing Error Class Magento\Catalog\Model\Indexer\Category\Product\Action\Full\Interceptor does not exist Magento Version 2.3.5

Solving Magento Indexer Error: Class Not Found

Introduction

As a senior developer working on multiple e-commerce projects, I often encounter issues related to Magento indexers. In this post, we’ll tackle the common error message you’re facing in your Magento 2.3.5 installation.

Understanding The Error

The error log indicates that Magento is unable to find the Magento\Catalog\Model\Indexer\Category\Product\Action\Full\Interceptor class during the index rebuild process. This usually occurs due to permission issues or problems with the autoload generation.

Debugging The Issue

Step 1: Verify Directory Permissions

The error message suggests that the ‘generated’ directory has read-only permissions, preventing Magento from generating the required classes dynamically. To fix this:

chmod -R 775 generated

Replace generated with the full path to your Magento installation’s generated folder.

Note: This command grants read, write, and execute permissions recursively to all files and directories within the generated folder for the user running PHP.

Step 2: Rebuild Autoload Files

Even after fixing the permissions, you may still encounter issues. To ensure that Magento can autload your classes correctly, run:

bin/magento setup:di:compile

This command triggers a compilation of all dependency injection (DI) configuration files and generates the required interceptor classes.

Step 3: Reindex Your Database

After successfully running the setup:di:compile command, reindex your database to apply the changes:

bin/magento indexer:reindex

Important: Make sure you have backups of your core_config_data and eav_attribute tables before proceeding with this step.

Troubleshooting Common Issues

1. Incorrect File Ownership

Even if you’ve granted the necessary permissions, the files might still be owned by root or a different user than the one running PHP (e.g., the web server user). Use chown to change ownership:

sudo chown -R www-data:www-data generated

2. File System Encryption

If you’re using a file system with encryption (such as APFS on macOS), Magento might have trouble generating files during compilation. Ensure that your file system is compatible or use an encrypted volume that doesn’t interfere with Magento’s autoload generation.

Best Practices To Avoid This Error

  1. Use Composer: Always install Magento via Composer to ensure proper dependency management and autoload configuration.
  2. Maintain Permissions: Regularly check and maintain the necessary permissions for critical folders.
  3. Avoid Manual Class Editing: Directly editing core classes can lead to conflicts during updates or reindexing.

Conclusion

In this post, we’ve explored a common Magento 2 indexing error and provided practical steps to resolve it. By understanding your system’s environment and following the suggested troubleshooting procedures, you should be able to overcome this issue successfully.

Remember to always consult the official documentation for further guidance on maintaining a stable and secure Magento installation: https://laravelcompany.com/magento-development-resources.

Happy coding!

Magento 2 Catalog Indexing Database

Our network