Should not be a problem. I guess the "btrfs-balancer allocation" found more free space than 13153337344 bytes and just skipped balance?
Your estimate on your usage pattern underlines the assumption of "no balance" necessary.
Mine went literally in seconds. I know heavy moving of podcast files recently "disturbed" the silence of my btrfs, so i was expecting balance and would have done allocation check manually if not proposed by installer