#mark-reckard_unexpected
dusty crescentBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1365343134245982400
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
rapid flame
pi_3RHU43CMpnBh61hX1HVMEfMW
obtuse pike
Thanks, looking
Yeah this does look like a test mode quirk -- I agree that the Charge should move to failed here and the refund should be canceled.
I'll file a ticket internally so we can get this behavior to mirror what happens in live mode here.
rapid flame
Ok awesome. Do you have an estimate for when this behavior might be changed to mirror live mode? Obviously you have no real idea, but just trying to get a ballpark. Weeks? Months?
We're considering deprioritizing this async refund work for a few sprints, so the timing here impacts that decision. And I totally understand if you can't give me an answer.
obtuse pike
Yeah sorry I really can't say -- that will depend on the priortization of the Eng team.
You should be able to just mock responses here to get the expected behavior.
rapid flame
Yeah we can mock expected behavior locally and in spec at least for now. Might just have to make and refund some real payments in a production sandbox as well. Thanks again for the information here