Asset Indexes update causes server blocking and requires admin page to remain open

[nikolenko-dmitriy]

Description:

I'm experiencing issues with Asset Indexes in Craft CMS 5 when working with approximately 15,000 assets.

Current Behavior:

When clicking the Update asset indexes button for all volumes in the Control Panel (Utilities → Asset Indexes):

1. The indexing process sends numerous HTTP requests to index.php?p=actions/asset-indexes/process-indexing-session (several requests per second)
2. This flood of requests causes the production server to block my IP address
3. The admin page with Utilities → Asset Indexes must remain open for the indexing to complete - if the page is closed, the process stops working
4. This occurs even though the queue is configured to run via cronjob with runQueueAutomatically set to false

The Problem:

The asset indexing process runs as a frontend Ajax-based process instead of being queued as a background task in the Craft Queue system.

Workaround:

The console command ./craft index-assets/all works perfectly for this use case because:

• It runs as a CLI command on the server
• It has access to maximum resources (no memory_limit, max_execution_time restrictions)
• It completes successfully without any issues

Similarly, the queue system runs via cronjob, so it also has no resource limitations.

However, this workaround isn't viable for our case because:

• The client (admin user) needs to trigger indexing themselves after uploading new images via FTP
• They don't have the knowledge or server access to run console commands

Expected Behavior:

The "Update asset indexes" button in the Control Panel should queue the indexing operation as a background job in the Craft Queue system (similar to how other heavy operations work). This would:

• Run through the cronjob with full server resources
• Not require keeping the admin page open
• Not flood the server with rapid HTTP requests
• Allow completion even with 15,000+ assets

Environment:

• Craft CMS 5
• ~15,000 assets
• runQueueAutomatically = false (queue runs via cronjob)

Question:

Is there a way to configure the Control Panel's "Update asset indexes" button to add jobs to the queue system instead of running as an Ajax-based frontend process?