I'm trying to find documentation on how the queue system works, and what parts of craft relies on it. To my current understanding, the queue is normally executed when users are logged in to admin, and search indexes are updated via queue?

Also, I use webhooks, which seems to be executed the same way.

Publishing pending posts though, doesn't seem to use the queue?

I don't have any queue/listen task running, but since I'm running a dockerized version I could run a parallel container which just invokes craft queue/listen if needed, would that be favorable, and then I would disable the runQueueAutomatically setting I assume?

Since I'm also running this in AWS, I have the option to run the queue via SQS, what would be the benefits of that? I assume the default queue is just stored in the database, but I assume it is doing some sort of locking to prevent multiple executions, if I would have multiple queue daemons running. So only real benefit would then be, that the information isn't stored in database (thus, not part of backups for instance), because the load on the database seems abysmal for any normal scenario.


"How does X work?" is a very broad question, and not one I intend to try and answer in detail here. Below are a few resources that should help get you started:

Robust queue job handling in Craft CMS

How to best design large queue jobs?

Also, here are all questions tagged with queue:

Hope that helps!!

  • Thanks for the links. I could have been clearer in the original question, I was primarily interested in how the execution of the queue works (by default), and what native parts of Craft actually uses the queue. I wanted to assess which part of my installation is affected by changes to the queue execution (by SQS, or separate worker, for instance) – jishi Feb 4 at 12:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.