diff --git a/docs/runtime/known_issues.md b/docs/runtime/known_issues.md
index 69db241a1ea1f6a92bbdff306aa40c2b8ab34f66..ccf43d7241ca1931875fa68b37ad8e89629ca758 100644
--- a/docs/runtime/known_issues.md
+++ b/docs/runtime/known_issues.md
@@ -28,4 +28,6 @@ The current implementation of Reowolf has the following known issues:
 
 - There is an assertion in the interpreter that makes sure that there are no values left on the expression stack when a statement has completed. This is not true when you have an expression statement! If you want to remove this assertion make sure to clear the stack (using the method on the `Store`).
 
-- The TCP listener component should probably do a `shutdown` before a `close` on the socket handle. Also it should set the `SO_REUSEADDR` option.
\ No newline at end of file
+- The TCP listener component should probably do a `shutdown` before a `close` on the socket handle. It should also set the `SO_REUSEADDR` option.
+
+- The way in which putting ports are ordered to block if the corresponding getter port's main inbox is full is rather silly. This lead to the introduction of the "backup inbox" as it is found in the runtime's code. There is a design decision to make here, but the current implementation is a bit silly. There are two options: (a) have an atomic boolean indicating if the message slot for an inbox is full, or (b) do away with the "main inbox" alltogether, and have an unbounded message queue.
\ No newline at end of file