diff --git a/docs/runtime/04_known_issues.md b/docs/runtime/04_known_issues.md
index 2fa7b4437d7e3ce4074a471796d081418566c744..4389a6bd4f015a6579d0778c04bda549741cfcb1 100644
--- a/docs/runtime/04_known_issues.md
+++ b/docs/runtime/04_known_issues.md
@@ -42,4 +42,6 @@ The current implementation of Reowolf has the following known issues:
 
 - The `Ack` messages that are sent in response to `PeerPortChanged_Block` messages should contain the sending components `(component ID, port ID)` pair in case the `PeerPortChanged_Block` message is relayed. When such an `Ack` message is received, the peer of the port must be updated before transferring the port to the new owner.
 
-- The compiler currently accepts a select arm's guard that is formulated as `auto a = get(get(rx))`. This should be disallowed.
\ No newline at end of file
+- The compiler currently accepts a select arm's guard that is formulated as `auto a = get(get(rx))`. This should be disallowed.
+
+- The work queue in the runtime is still a mutex-locked queue. The `QueueMpsc` type should be extended to be a multiple-producer multiple-consumer queue. This type should then replace the mutex-locked work queue.
\ No newline at end of file