Weird to hear - I wouldn’t expect we’d ever return an HTTP 202! If you see it again, I’d love to find out the x-nf-request-id of that response so I could look at it a bit more closely in our internal logs:
Apologies, but I wasn’t quite sure if you had managed to get this working well enough for your purposes or if you still needed debugging help?