Issue¶

When running the export queues for Acquia Content Hub, it will successfully complete the run, but leave entities queued without any errors.

[success] Processed 0 items from the acquia_contenthub_publish_export queue in 0.04 sec. [1.06 sec, 45.35 MB]

Resolution¶

Check the queue table to see if the entities have a non-zero expire field:

drush -l <site url> sqlq "SELECT * FROM queue WHERE name='acquia_contenthub_publish_export';"

The second to last field is the expire field; if it has a non-zero value, the item is expired and Content Hub will not attempt to export it:

555555	acquia_contenthub_publish_export	O:8:"stdClass":2:{s:4:"type";s:17:"node";s:4:"uuid";s:36:"1a6e2e87-d4d5-4e52-8b09-cf11ae1ea111";}	1611374858	1611270151

Expired entities should not block other exports; Content Hub will continue through the queue and process non-expired entities.

These entities can be removed from the queue or, if the initial issue that prevented export has been resolved, the expire value can be set to zero:

drush -l <site url> sqlq "UPDATE queue SET expire=0 WHERE name='acquia_contenthub_publish_export';"

Cause¶

If an entity fails to export, Content Hub will assign it an expire value and not attempt to export it again as long as the expire value does not equal zero.  This is to improve processing performance and avoid trying to process ineligible entities.

After setting the expire values to zero, it may be worth manually running the queue with Drush and the very very verbose option to see if errors recur. This will help identify the issue if they fail to export again:

drush -l <site url> queue-run acquia_contenthub_publish_export -vvv