The subject condition happens when a large number of clients have sessions opened on the Remote Storage Server. The file is eventually, recalled, but the client receives no notice.
You can reproduce this behavior by starting 42+ active sessions.
There is currently no workaround for this issue, which doesn't impact the server's performance.