But webcron is running fine, so I must admit that I do not get it why this message shows up then?
Am I missing something? In the documentation it refers to setting up cron, but that is already done, so please enlighten me. 
Kind regards
AngryWarrior
If your server supports queues it can make the app respond quicker, there’s more info here:
https://invoiceninja.github.io/docs/self-host-installation/#final-setup-steps
It seems “Health Check” is wrongly showing not working queue (or it is really not working) and it changed after last updates.
Active cron:
What queue setting do you have in the .env file?
Sorry, never mind. I see it in the screenshot above, I think you need to update the .env file to enable the queue.
I see, QUEUE_CONNECTION=sync was wrong setting. I changed it to database and warning disappeared. Thank you for help.
is this instruction for running IN via docker? (I don’t think so as I can’t find a .env file right now)
What is really the advantage of setting queues up @hillel?
For us, we’re just sending a few invoices a month so I don’t know if this is worth spending time on…
Thanks in advance.
Kind regards
AngryWarrior
It enables the frontend to respond quicker by having the backend queue the request, rather than immediately processing it.
For example, if you click “Send email” in the app without queues enabled the app needs to wait for the email to be sent which can take a few seconds.
Thanks for the explanation, Hillel. 
So it would be a minor improvement in response time for us in regards to that we only generate a few invoices right?
When looking into the documentation it doesn’t really mention anything about doing it in Linux environment directly, only C-panel from what i can read there:
We’re running a Ubunto server for this without C-panel Although we have installed Webmin on it to make things a bit easier.
Kind regards
AngryWarrior
Webcron only executes the scheduled tasks such as recurring invoices / reminders.
If you have QUEUE_CONNECTION=sync. Then any required actions are performed during the request cycle (ie sending emails / generating PDFs)
If you wish to use QUEUE_CONNECTION=database, the system will try its best to start and run the queue’s for you. However depending on platform this may or may not work.
