[6.11.5] Shares with "Use Cache Pool = Yes" run out of space when cache is full instead of spilling over to array.

I'm running Unraid 6.11.5 and have run into a situation that seems to run counter to the documentation regarding the use of Cache for shares.

• A share called "media" on the array.
• It is configured to "Use cache pool (for new files/directories): Yes"
• It has 4.5 Tb of free space.
• The cache is 500 Gb on an nvme drive.
• It's served via SMB over the network and accessed from a Windows 11 client machine.

When copying about 1 Tb of files (each file is 1-2 Gb in size) from Windows to the share over the network, the cache fills up and the following happens half way through the copy:

• Windows copy errors and reports that an additional 500GB or so are required to continue copying.
• Warnings notifications appear in Unraid saying the cache drive is full.
• Docker and VM's running on the cache drive error out and pause/shut off (appdata and domains are set to "Prefer" cache)

To recover from this situation:

1. I manually kick off mover. It begins to move the files from cache to the array. As it does so, free space on the cache drive returns.
2. In windows, I can click "Try again" on the copy and it will resume copying the files until the cache drive fills up again.

According to the documentation, I would expect that when the cache drive is exhausted, new files are put directly onto the array and the copy from the perspective of the windows client continues uninterrupted (unless the array was out of space, which isn't the case). From the help:
 

Quote

Use cache pool (for new files/directories): Yes indicates that all new files and subdirectories should be written to the Cache disk/pool, provided enough free space exists on the Cache disk/pool. If there is insufficient space on the Cache disk/pool, then new files and directories are created on the array. When the mover is invoked, files and subdirectories are transferred off the Cache disk/pool and onto the array.