I'm not sure what you mean by "lnurl says outdated". Sending zaps doesn't have anything to do with the lnurl attached to your profile, but rather with your sending wallet.

I put the wallet info in these fields and it will receive but won't send. Thought it might have to do with the outdated message

Maybe send a screenshot of what you see when you send?

Just spinning wheel where zap icon is

Ah, ok, this has always been difficult. Your payments are likely going through (are they, if you check your wallet?), but the zap isn't showing up where coracle is looking for it. What wallet are you using to zap?

Sorry if I mislead. using amethyst. And wos

@Vitor Pamplona @Wallet of Satoshi any ideas? I frequently run into the same issue on Coracle/Alby. I don't think it's my implementation (any more), I can only guess that the zapper isn't delivering the zap receipt to the proper relays on time

Yeah, the zapper didn't send the confirmation. I wonder if @Parallel Structures has too many inbox relays that the zapper from Alby doesn't know what to do... Amethyst does create the zap request with ALL of them, for all involved parties in the zap, so the list can be massive and may even hit the maximum json size limit in some relays (given that the zap request goes inside the zap event). @Parallel Structures see if you drop the outbox/inbox relay list to just the 3 that you trust the most helps.