pull down to refresh

This may simply be an issue with how I interface with SN, and the solution may just be to change my behavior (especially if I'm the only person impacted by this), but figure I'll put this out there in case others are also experiencing it.
About once or twice a day, a zap fails. No big deal by itself, since there's a handy "rezap" option.
But the only way I know a zap has failed is if/when I go to the notifications page. Even when the red notification button is on, I don't aways go there immediately; I may be more interested in reading a post on the front page (or multiple posts -- I'm surely not the only one who opens a bunch of items in tabs at once), or comments on a thread I've already got open, etc.
I also, of course, may be doing non-SN things on other sites (shocking, but it happens).
As a result, sometimes I only find out a zap failed hours later. That's not the end of the world, of course. Maybe it costs me a few sats if I zapped a post early but it failed. Maybe, on rare occasions, it costs the poster a few sats in rewards because my re-zap takes place the next day. But there's not a huge impact, other than it being something that I want to fix.
But I do want those zaps to go through quickly, if for nothing else as a way to tell the poster/commenter that their content was worthwhile!
One solution, of course, is to always follow up on every zap I make and make sure I see it go through. Beyond a lack of time, I'm way too disorganized for this option.
Another one, I suppose, would be to check my notifications constantly, or (dear god) enable push notifications. I do not like this one, as it would directly impact the enjoyment I get from SN.
A third option is to do nothing. As noted, it's not the end of the world, and both of the solutions seem like ones that would make things less enjoyable for me.
But a solution that might work, if this is something that impacts others and if it's something that can be done without making the UI of SN worse overall, would be some way to differentiate notifications. Maybe a different color alert if there's a failed zap? Maybe a different icon popping up alongside the cowboy hat and other ones (a rattlesnake?)?
Like I said, this may only be a "me" thing, in which case it's mine to deal with, but figured I'd see if there are others who experience it, and may have other ideas for solutions.
163 sats \ 5 replies \ @k00b 14h
We have a pull request in the final stages of review that will retry failed paid actions automatically in the background. These notifications will only surface after they fail repeatedly.
ek has been mia (moving I think?), but if he doesn't come online soon, I'll take it to the goal line myself.
reply
Excellent news! I expect that will resolve things from my end without having to change my behavior (my favorite kind of solution).
reply
49 sats \ 1 reply \ @grayruby 14h
Will it retry right away or a specific intervals like 10 mins, 30 mins, 60 mins etc.
reply
40 sats \ 0 replies \ @k00b 14h
We could do an exponential backoff, but the majority of errors I've seen wouldn't benefit from it. These zaps usually fail because of some temporary one-off thing, or because the receiver is using a zap locker (they forget to accept the payment by opening their wallet and it times out). To start, it'll simply be a succession of retries iterating through receiving and sending wallet fallbacks a couple times.
reply
83 sats \ 1 reply \ @k00b 14h
We also have other plans for repurposing the horse and gun badges so you all can communicate your wallet statuses to each other in a fun way which should give more confidence in zap outcomes. Might be a minute for that change though.
reply
Aardvark badge when?
reply