Admin Reindex: Queue-backed Magento reindexing from the Admin
Admin Reindex adds selected and Select All reindex actions to Magento’s native Index Management grid, then moves the work into Magento bulk operations and a message-queue consumer so the Admin request does not stay open.
Magento 2PHPMessage QueueBulk OperationsACL and Lock Manager
The useful part of a case study is the reasoning: what was risky, what was shipped, and what proof the team had after release.
Operational problem
Magento store operators can inspect indexer status in System > Tools > Index Management, but scheduling selected indexers normally requires command-line access or a separate operational process. The extension needed to add that control without holding an Admin request open or bypassing Magento permission boundaries.
Technical architecture
The module stays inside Magento’s existing admin and asynchronous-processing systems instead of building an isolated reindex screen.
A native mass action is added to the core Index Management grid for selected rows and Select All.
A dedicated Reindex Data ACL resource controls who can schedule work.
The request creates a Magento bulk operation and publishes indexer jobs to a message-queue consumer.
Progress is scoped to the Admin user who created the bulk job.
Concurrency and failure handling
Reindexing changes catalog-derived data, so the failure model matters as much as the button that starts the job.
Lock Manager and Magento indexer state checks prevent conflicting work.
Indexers already reported as running are skipped safely.
A failed indexer does not prevent later queued indexers from continuing.
The Admin receives an escaped summary while the complete exception stays in Magento logs.
Public release and operating requirements
Version 1.0.0 is published under the MIT license with Composer installation, source code, documentation, compatibility notes, and a public issue tracker.