The refund did not work even after 24 hours. However, the middleway(swap service provider working with Boltz software in the backend) person kept me updated on the process throughout. I helped debug the issue a little by sending screenshots of the console while requesting a refund. He had to raise a GitHub issue and tried tweaking this manually, and it worked. I finally have my sats back. Otherwise, I would have had to wait 7 days(block height till timeout). I do not know what technically happened in detail, but I learned a lot from swaps in the process. In summary, if a user's feedback for production software leads to a GitHub issue, I conclude that swaps(at least on-chain to LN) are not ready for prime-time. Though I appreciate the middleway person sticking with me(having some tough conversations) till the issue got resolved.