Native Reindex and Reset
Adds both operations to System > Tools > Index Management instead of replacing the core grid with another admin page.
Free & open source · Magento 2
Reindex Magentowithout leavingthe Admin.
Reindex or reset selected indexers from Magento's native grid, follow live progress, and get an early warning when the background worker is unavailable.
- Access
- Free and open source
- Release
- Version 1.1.0
- Compatibility
- Magento 2.4.4–2.4.9
- Distribution
- Composer + GitHub
See it in action
Start an operation in the grid and keep working
The animation demonstrates the Reindex flow. Reset uses the same queue-backed progress workflow in version 1.1.0.
What it handles
Background operations, not a second index-management screen
The module adds Reindex and Reset to Magento's native grid and uses Magento services for permissions, locking, queueing, health checks, and progress.
Worker-health warning
Warns administrators when no working consumer path is detected, before queued jobs appear to stall silently.
Duplicate-job protection
Reuses progress from an active operation when the same indexer is already pending or running instead of queuing it twice.
Progress you can follow
The popup combines new and active operations and shows running, completed, skipped, failed, and remaining indexers.
The page can be closed
Once 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, LockManager, cron history, indexer APIs, and the native admin UI.
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 or Reset. The extension validates permissions, checks worker health, and reuses active work before scheduling anything new.
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 checks for a working consumer path before scheduling and shows a warning when none is detected. It never starts 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 does Reset do?
Reset uses Magento's native invalidate operation, matching bin/magento indexer:reset, and schedules it through the same background workflow as Reindex.
What happens if the background worker is not detected?
Index Management shows a warning before scheduling. The job can still be queued, but it will not run until Magento's consumer path starts processing messages.
Can the same indexer be queued twice?
Not while an Admin Reindex bulk operation for that indexer is pending or running. The extension reuses the existing operation and shows its progress.
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.
Release notes
What changed in each version
Review new features, operational changes, and deployment guidance before updating the module.
VersionCurrent
1.1.0
- Added background Reset beside Reindex and replaced Magento's duplicate synchronous Invalidate index action.
- Added a worker-health banner based on the consumer lock, pending-operation age, last processed timestamp, and consumer cron history.
- Added a pre-scheduling worker check while still allowing jobs to remain queued for later processing.
- Added a race-safe deduplication guard that reuses progress from active operations instead of queuing the same indexer twice.
- Added multi-bulk progress aggregation when a selection contains both new and already-active indexers.
- Documented Magento LockManager providers and multi-node deployment safety.
Version
1.0.0
- Added the secured Reindex action to Magento Index Management.
- Added background execution through Magento Bulk Operations and Message Queue.
- Added live progress with completed, running, skipped, failed, and remaining indexer states.
- Added scoped ACL, operation ownership, sequential locking, failure isolation, and complete exception logging.
- Added Magento 2.4.4 through 2.4.9 compatibility checks and Composer distribution.
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.