Oh, that would be quite a terrible way of handling a service overloading if the endpoints just say “it’s fine i did what you want” (204) but actually didn’t really, and corrupts the data in the background (or something like that that’d be source of the 500)
I’m using it as well to cleanup followbot raids while the raid is happening (instead of cleaning it up after) so it’s intended to potentially do bunch of requests in a short amount of time.
Thank you for your super fast answer !