Job queue – dealing with stuck records I have a cron job that gets stuck because I have a loop claiming items from the queue that ends on numberOfItems() == 0, which never happens because one of the queue items is stuck and cannot be claimed.

Clearly this is a flaw on my side, but I am trying to understand how to best address it. The claimItem() method returns FALSE every time in this case, so it should be easy to handle cases of bad queue processing, for example:

while ($item = $queue-&gt;claimItem()) {
    // process item
}


However, what if the first queue item is "faulty", while there are other queue items that are perfectly fine? I will never be able to retrieve them in this method. It also seems impossible to move on to the next item in the queue if claimItem() returns false (please correct me if I am wrong).

What is the correct way to handle such cases with Drupal's queue?
When looking at the code from the claimItem method it only returns FALSE if no items are available to claim.

So if $queue-&gt;claimItem() returns FALSE you can be sure that all available items are claimed (or failed to be claimed).

public function claimItem($lease_time = 30) {
  // Claim an item by updating its expire fields. If claim is not successful
  // another thread may have claimed the item in the meantime. Therefore loop
  // until an item is successfully claimed or we are reasonably sure there
  // are no unclaimed items left.
  while (TRUE) {
    try {
      $item = $this-&gt;connection-&gt;queryRange('SELECT data, created, item_id FROM {' . static::TABLE_NAME . '} q WHERE expire = 0 AND name = :name ORDER BY created, item_id ASC', 0, 1, [':name' =&gt; $this-&gt;name])-&gt;fetchObject();
    }
    catch (\Exception $e) {
      $this-&gt;catchException($e);
      // If the table does not exist there are no items currently available to
      // claim.
      return FALSE;
    }
    if ($item) {
      // Try to update the item. Only one thread can succeed in UPDATEing the
      // same row. We cannot rely on REQUEST_TIME because items might be
      // claimed by a single consumer which runs longer than 1 second. If we
      // continue to use REQUEST_TIME instead of the current time(), we steal
      // time from the lease, and will tend to reset items before the lease
      // should really expire.
      $update = $this-&gt;connection-&gt;update(static::TABLE_NAME)
        -&gt;fields([
          'expire' =&gt; time() + $lease_time,
        ])
        -&gt;condition('item_id', $item-&gt;item_id)
        -&gt;condition('expire', 0);
      // If there are affected rows, this update succeeded.
      if ($update-&gt;execute()) {
        $item-&gt;data = unserialize($item-&gt;data);
        return $item;
      }
    }
    else {
      // No items currently available to claim.
      return FALSE;
    }
  }
}