I think if the zaps failed on PWA, the
retry also would occur. But the way "undoable zaps" are implemented, the zaps sit on your client for 5 seconds before actually being sent to the server, so if you close the app/webpage before that 5 seconds is up, it's like it never happened.reply
since I use undoable zaps - > ugh you mean you enabled zap undos 😂
so if you close the app/webpage before that 5 seconds is up, it's like it never happened.
hmmmm, but isn't it default-zapped if you don't click the undo? So closing it before the 5s is like you didn't and can't click the undo.
reply
hmmmm, but isn't it default-zapped if you don't click the undo? So closing it before the 5s is like you didn't and can't click the undo.
@ek can confirm, but I believe that is the case
reply
That's how it works. It's happened to me too. If you close the window before 5 seconds the zap doesn't go through.
reply
@WeAreAllSatoshi’s description here is correct:
But the way "undoable zaps" are implemented, the zaps sit on your client for 5 seconds before actually being sent to the server, so if you close the app/webpage before that 5 seconds is up, it's like it never happened.
but this is wrong (as I read it):
hmmmm, but isn't it default-zapped if you don't click the undo? So closing it before the 5s is like you didn't and can't click the undo.
If the zap is pulsing, you need to let it finish else it won’t arrive on the server. So if you close the window before it’s finished, the zap never happened (just like @WeAreAllSatoshi described).
Calling it „undo“ is the confusing part, it’s technically more a delay.
reply
Yep, that's exactly what I thought. At first, I kept thinking it had bugged out a few times, but it hadn't. Then I figured it out. 'Delay' is the word.
reply
retryoption, not sure how it works in SN pwa.