Backfill returns 202 but Push notifications never arrive at webhook

Hello,

I'm integrating with the Garmin Health API using OAuth2 PKCE and the Push service. Normal push notifications (new data synced from device) are working correctly and arriving at my webhook without any issues. However, backfill push notifications never arrive, even after waiting several days.

Here is what I have confirmed so far:

- OAuth2 PKCE flow is working correctly
- My webhook endpoint is publicly accessible and responds with HTTP 200 within 30 seconds
- New push data (dailies, sleeps, etc.) arrives at the webhook normally
- Backfill requests return HTTP 202 (Accepted) as expected
- Subsequent backfill requests for the same user return HTTP 409 (Duplicate), confirming the first request was registered
- I have waited several days after the backfill request with no notifications arriving

The summary types I am requesting backfill for are: dailies, sleeps, bodyComps, skinTemp, pulseox, bloodPressures, activities, and mct.

The backfill is triggered right after the user completes the OAuth2 flow for the first time, using the access token obtained during authorization. The date range requested is from one month ago to the current timestamp in Unix seconds.

I noticed that my Partner Verification currently shows missing deregistration and user permissions change endpoints, which I am working on adding. However, since normal push notifications work fine, I am not sure if this would be the root cause of backfill notifications not being delivered.

My questions are:
1. Is there any known delay or queue backlog that could cause backfill notifications to take more than a few days to be delivered?
2. Could the missing deregistration/permissions endpoints in Partner Verification block backfill notification delivery specifically?
3. Is there a way to check the status of a backfill request on your end for a specific user ID?

Any help would be greatly appreciated. Thank you.