This is most likely a bug. It certainly is unexpected and should be reported to Databricks support or your platform administrator for clarification and remediation.

• As a temporary workaround, running vacuum commands outside of threaded contexts or scheduling them sequentially may avoid the issue until a fix is implemented.