Getting "a new asynchronous event" warning in container logs

[adamblaine]

Getting this in the watchlistarr docker container logs:
Your app's responsiveness to a new asynchronous event (such as a new connection, an upstream response, or a timer) was in excess of 100 milliseconds. Your CPU is probably starving. Consider increasing the granularity of your delays or adding more cedes. This may also be a sign that you are unintentionally running blocking I/O operations (such as File or InetAddress) without the blocking combinator.

Dedicated docker cpu usage is low, not seeing anything that would indicate its struggling at all. Is there anything that might be causing this?

[EMeric1992]

I have exactly the same issue with my configuration...