Understanding -402 Response Limit for makeWebRequest?

I'm trying to understand what defines the limit at which makeWebRequest starts returning a -402 response code.

In my case, a user is encountering this error with significantly less data than I see in my own tests. He’s using a Fenix 7 Pro, paired with an Android 13 phone and Garmin Connect 5.14. The request starts failing for him with around 32 kB of JSON response data.

In contrast, I'm able to handle up to 44 kB of JSON:

• In the simulator

• On my Epix 2 Pro (which I believe is very similar to the Fenix 7 Pro, aside from the display)

One key difference: I’m on iOS, while he's on Android. I tried changing the phone OS in the simulator settings, but regardless of whether I set it to iOS or Android, I can still process up to 44 kB without issue.

Does anyone know:

• What actually determines when a -402 is triggered?

• Could the phone OS, Garmin Connect version, or watch model affect this limit?

• Is there any official documentation or known variability in how makeWebRequest handled this limit?

Any insights would be greatly appreciated!