- 🇺🇸United States TomTech
Automatically closed because Drupal 7 security and bugfix support has ended → as of 5 January 2025. If the issue verifiably applies → to later versions, please reopen with details and update the version.
Duplicated items can be created in the queue commerce_license_expiration. And duplicate items update the same license multiple times.
There are cases where we want each license to get expired only once and this issue can be problematic for such cases.
This problem can occur if the worker callback commerce_license_expiration_queue_process() takes a relatively long time compared to commerce_license_cron().
Steps to reproduce:
expires.commerce_license_cron.There are some options.
a) is the best if we have a good way to prevent duplicated items but it's basically impossible without using a dirty manner.
So currently b) is the only implementable approach, I think.
FYI, there are some attempts for the unique queue function.
Adopt the approach b) and make the worker callback idempotent for licenses.
(None)
(None)
(None)
We had an issue where the same 2 entries for 'commerce_license_expiration' were repeatedly added to the 'queue' table during cron runs.
These 2 entries were failing a custom function to update a Mailchimp subscriber list and as a result were not being processed and removed from the queue. The failure was due to the users to whom these license relate having been deleted from the 'users' table.
The net result of these entries failing processing was that the 'queue' table became over-populated to the point that no subscriptions were being expired.
The patch prevents the addition to the 'queue' table of an pre-existing entry.
Closed: outdated
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Automatically closed because Drupal 7 security and bugfix support has ended → as of 5 January 2025. If the issue verifiably applies → to later versions, please reopen with details and update the version.