Magento 2.4.1 cron job doesn't run

[Alldo Group]

We added a product to another store view, and the new product URL in the new store view didn't make use of URL rewriting, so we tried to update the product attributes via:

Catalog => Products = Actions => Update Attributes.

Nothing happens and the admin is showing:

Task "Update attributes for 1 selected products": 1 item(s) have been scheduled for update.

We have tried the following with no success:

1. php bin/magento cron:remove
2. php bin/magento cron:install
3. php bin/magento cron:run

Command:  bin/magento queue:consumers:list

product_action_attribute.update
product_action_attribute.website.update
exportProcessor
inventory.source.items.cleanup
inventory.mass.update
inventory.reservations.cleanup
inventory.reservations.update
media.storage.catalog.image.resize
codegeneratorProcessor
inventory.reservations.updateSalabilityStatus
inventory.indexer.sourceItem
inventory.indexer.stock
media.content.synchronization
media.gallery.synchronization
async.operations.all

We run FreeBSD 12 if that might be a concern.
Can someone please shed some light to this please?

Thank you,

[gaurav_harsh1]

Hello @Alldo Group 

Check the below solution, it may help :

https://community.magento.com/t5/Magento-2-x-Technical-Issues/Attributes-stuck-in-pending-update/m-p...

[Alldo Group]

Thank you for your answer!

I actually already tried to change the date to a later one, directly in the table, and that didn't work.

All cron jobs seems to be working just fine, but the notice in admin still exists.

Any more suggestions?

[2020-10-22 04:56:01] main.INFO: Cron Job bulk_cleanup is run [] []

[2020-10-22 04:56:01] main.INFO: Cron Job bulk_cleanup is successfully finished. Statistics: {"sum":0.00060915946960449,"count":1,"realmem":0,"emalloc":5744,"realmem_start":35651584,"emalloc_start":32143744} [] []

[2020-10-22 04:56:02] main.INFO: Cron Job consumers_runner is run [] []

[2020-10-22 04:56:02] main.INFO: Cron Job consumers_runner is successfully finished. Statistics: {"sum":0.028512001037598,"count":1,"realmem":2097152,"emalloc":106952,"realmem_start":27262976,"emalloc_start":24816056} [] []

[gaurav_harsh1]

@Alldo Group 

Once you truncate the database table, the error will no longer visible, and after clearing if your cron is not correctly set up, it will show as warning as it can't work properly without cron.