Docs note suggestion about Companion state

[netdown]

Hi,
I just noticed an issue with my Companion server configuration, but did not go after in depth so I am not sure about the reasons. Anyways, I suggest at least updating the docs with the information below. I was running the server on Google Cloud Run, which automatically deploys multiple containers if the number of concurrent requests exceed the configured amount. It seems that Companion fails to make download requests if multiple containers are involved. There must be some kind of state which it expects to be available across all requests of a download batch (in this case, download batch means a group of images which are downloaded in the same queue). Download requests handled by the first container resolve correctly, for the rest, the WS connection is opened, but there are no messages at all.

[Murderlon]

Thanks for the report but it is a duplicate of #3538

[Murderlon]

We are planning to completely overhaul the companion docs so this will be tackled.