@Edent ugh it naively makes sense to delete records but unfortunately you always have to keep them around for some period of time and have a flag. I think every developer (myself included) has made this mistake at some point. I'm not sure if it's an issue with AP or just with whichever server implemented this.
@Edent Do you really need to validate a request to delete an user that was already deleted? What's the harm of a spoofed request? An unnecessary database lookup leading to DOS? It's not like you're going to delete it twice.
@Edent Check the logs in case the original deletion was recent. If the logs might have been deleted.. 🤷
Some big event-sourced systems keep every single event to be able to go back and check, but that kind of forever storage would be illegal in right-of-erasure jurisdictions.
@Edent would it hurt to just respond ok? If you don't know the user then you don't can't know the message either. If you were told to delete something you don't have, would you error, or just reply that it has been deleted?
@SDF hi - I think your instance might be misconfigured. You keep sending me delete messages for deleted users. I'm replying with HTTP 200 - but you keep sending the same requests over and over again. Is this something you're able to fix?