I’ve spent a few hours trying to figure this out however I haven’t progressed much so I thought I’d post here. I’m having issues with the Bulk Actions not starting, the task gets queued however that’s all it does, it doesn’t start. I get a Task “Update attributes for 20 selected products”: 0 item(s) are currently being updated.0 item(s) have been scheduled for update. and when I check the log, it says it’s ‘In Progress’ however nothing starts.
Troubleshooting
1.) I’ve checked the magento_bulk and deleted the rows, hoping there was something stuck however when I queued another task, it gets added to the table and doesn’t get pushed into magento_acknowledged_bulk. Is the job supposed to be pushed into this to actually run?
2.) I’ve checked the Nginx logs and can’t see anything which would point to an issue, there was an issue with post_max_size where the limit was being exceeded however I fixed this and restarted PHP, this didn’t have any effect on the bulk actions.
3.) I double-checked the permissions and can confirm they’re as Magento recommends, there’s nothing incorrect with the permissions.
Has anyone encountered this issue before? I looked through some forums however it doesn’t look like anyone had a fix for this?
Any help is greatly appreciated!
4
Answers
After some further investigation and looking around, this change in the env.php file seems to have fixed my issue. Before making the change, I cleared the magento_bulk table and ensured nothing was queued.
I replaced the default cron_consumers_runner with the following:
After changing this, I recompiled and cleared the caches before queuing up a bulk change (I changed the pricing of 20 products) and this job ran instantly.
I hope this helps others!
According to Magento 2 docs, you should leave consumers empty:
consumers – An array of strings specifying which consumer(s) to run. An empty array runs all consumers.
reference: https://devdocs.magento.com/guides/v2.4/config-guide/mq/manage-message-queues.html
In app/etc/env.php:
I had the same issue in Magento 2.4.2. But was fixed after changed the db-schema.xml as describes in this post How to Fix Magneto 2 Bulk Actions Not Starting
Actually for me on 2.3.2 this was really simple, there was a cron job in the database that was "stuck" and when I deleted it things started going again. e.g. in the database table
cron_schedule
look forjob_code = 'consumers_runner'
with astatus = 'running'
and delete that row. Hope that helps someone else, took me ages to figure out…