What is the purpose of the RabbitMQ connection?

[christianstrauch]

All,
I spent some time searching for an answer to this relatively trivial question:
What does the option to connect RabbitMQ do in the current implementation of KitchenOwl?
I use KitchenOwl with Postgres, and separate back- and frontends behind an SSL-terminating reverse proxy server, using OIDC against my IDP (which shouldn't have anything to do with my question.) In this scenario, I was hoping to be able to react to activities within KitchenOwl by listening to its events in RabbitMQ, which I connected by configuring the MESSAGE_BROKER environment variable to the AMQP URI of my RabbitMQ deployment, like so:
MESSAGE_BROKER=amqp://rmq-user:rmq-pwd@rmq-host. The connection succeeds, and KitchenOwl seems to be continuously polling - however, nothing seems to get published to the message broker.
Am I misunderstanding the intended use, is there something I should be changing to make this work, is this not implemented (yet,) or is this not intended to be used in my deployment scenario?
I'm using the docker images tagged "latest" for both -web and -backend.
Thanks all!

[TomBursch]

It is mainly used for scheduling recurring jobs. Without the broker setup, the main process is blocked during those daily/weekly/monthly tasks and cannot react to incoming requests. This is usually not a problem on self-hosted instances since there aren't many households and the tasks are completed quickly during the night. With the broker, the tasks are completed by subprocesses that listen for jobs, such that the main process can still react to requests.

If you want to listen for events, there is currently no simple solution. Maybe create an issue for it with the specific use case you have.
Thanks, Tom