Native Reindex action
Adds Reindex to System > Tools > Index Management instead of replacing the core grid with another admin page.
Free Magento admin extension
Reindex Magentowithout leavingthe Admin.
Select indexers in Magento's native grid, start the job, and watch progress while the queue handles the work in the background.
Magento Admin / Index Management
2 selected
Native actionIndex Management
ExecutionMagento queue
Failure modelContinue safely
- Access
- Free and open source
- Release
- Version 1.0.0
- Compatibility
- Magento 2.4.4–2.4.9
- Distribution
- Composer + GitHub
See it in action
Start the job in the grid and keep working
Select one or more indexers, choose Reindex, and follow the job without keeping the original admin request open. The animation shows the actual module flow.
What it handles
A reindex action, not a second index-management screen
The module adds the missing action to Magento's native grid and uses Magento services for permissions, locking, queueing, and progress.
Selected or Select All
Run one indexer, a selected group, or every indexer through Magento's existing selection controls.
Progress you can follow
The popup shows totals and the running, completed, skipped, or failed state of each selected indexer.
The page can be closed
Once the work is queued, closing the popup or leaving Index Management does not cancel the scheduled job.
Built on Magento services
Uses Message Queue, Bulk Operations, ACL, Lock Manager, indexer APIs, and the native admin UI.
One failure does not hide the rest
Already-running indexers are skipped, later indexers continue after a failure, and the full exception stays in Magento logs.
How it works
Select, schedule, and follow the job
The admin flow stays short. Magento handles ownership, persistence, locking, and queue execution underneath.
1
Select indexers
Open Index Management and choose one or more indexers, or use Magento's Select All control.
2
Schedule safely
Choose Reindex. The extension validates permissions and indexer state, then schedules a Magento bulk operation.
3
Follow live progress
Track progress in the popup, then close it or leave the page while the configured consumer continues processing.
Compatibility and installation
Ready for Magento 2.4.4 through 2.4.9
Supports Magento Open Source and Adobe Commerce. The PHP versions below follow the module's documented release matrix.
| Magento | Supported PHP |
|---|---|
| 2.4.4 | 8.1 |
| 2.4.5 | 8.1 |
| 2.4.6 | 8.1, 8.2 |
| 2.4.7 | 8.2, 8.3 |
| 2.4.8 | 8.3, 8.4 |
| 2.4.9 | 8.4, 8.5 |
Composer
Install the stable release
composer require haroone/module-admin-reindex:^1.0Magento setup
Enable and register the module
composer require haroone/module-admin-reindex:^1.0
php bin/magento module:enable Haroone_AdminReindex
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento cache:cleanIn production mode, include php bin/magento setup:static-content:deploy -f in the normal deployment flow for the small admin JavaScript and CSS assets.
Do not skip setup:upgrade
Magento registers the module's MySQL queue destination during recurring setup. Without it, jobs can appear scheduled but never start.
Queue requirement
Magento's consumers cron group must run
The extension schedules work through Magento's message queue. It deliberately does not start operating-system processes from an admin request.
Dedicated consumer
php bin/magento queue:consumers:start haroone.adminreindex.indexerPermissions and security
Controlled by Magento, scoped to the initiating admin
The module uses Magento's own permissions, form validation, bulk ownership, and output escaping rather than creating a parallel security model.
Dedicated Reindex Data ACL
Users without the Index Management child permission cannot schedule work or request progress.
Bulk job ownership
Progress is restricted to the admin user who created the bulk operation.
Magento-native persistence
Bulk Operations and Message Queue keep the scheduled job in Magento.
Safe output and logging
Admin output is escaped, while complete exceptions remain in Magento logs.
What the extension does not change
- Indexer modes
- Magento cache state
- PHP memory or time limits
- Store configuration
FAQ
What to know before installation
For implementation details, version changes, and troubleshooting, use the module README and GitHub Issues.
Does the extension change indexer modes?
No. It does not change indexer modes, cache state, PHP limits, or store configuration.
Does reindexing stop if I close the popup?
No. The admin request schedules background work. Closing the popup or leaving the page does not stop the queued job.
What happens when an indexer is already running?
The extension asks Magento for the working state and safely skips an indexer Magento reports as already running.
What happens if one indexer fails?
Later indexers continue. The popup shows a safe summary while the complete exception is written to Magento logs with the indexer ID.
Which cron process is required?
Magento's consumers cron group must run so the message-queue consumer can process scheduled reindex jobs.
Can every admin user run a reindex?
No. The module adds a dedicated Reindex Data ACL resource beneath Index Management, and progress is restricted to the admin user who created the bulk job.
Support and engineering
The extension is free. Magento engineering is available when the problem is bigger.
Use GitHub Issues for reproducible product bugs and feature requests. For store-specific module, migration, performance, or checkout work, send the store context directly.