Thank you for the guidance. As you suggested, I've submitted a code-level support request, referred by you with a link to this thread— it covers the APNs-returns-200-but-notifications-aren't-received issue with the affected device tokens and send logs we discussed. Happy to provide any additional tracing details as needed. Best regards

Thank you for the guidance. We're updating our logging ASAP to capture and retain the apns-id from the APNs response headers for future cases. But some current "not received" cases happened before that logging existed, so we have no apns-id for them. Could you investigate these using just the push token and approximate send time? We have the tokens and timestamps. Also, we'd rather not post tokens or apns-id publicly, to avoid misuse. Is there a private channel (email or support) to share them?

Thank you for the guidance. We're updating our logging ASAP to capture and retain the apns-id from the APNs response headers for future cases. But some current "not received" cases happened before that logging existed, so we have no apns-id for them. Could you investigate these using just the push token and approximate send time? We have the tokens and timestamps. Also, we'd rather not post tokens or apns-id publicly, to avoid misuse. Is there a private channel (email or support) to share them?