Dropping of telemetry events

Start by reviewing the reported event timeline, the bad-network transition, and the change to the BestEffort transmit profile. Determine whether events are being dropped during the four-hour gap and document the expected callback behavior for dropped telemetry; the issue provides no file, test, or entry point to run.

Describe your environment. Describe any aspect of your environment relevant to the problem, including your SDK version, platform, OS version, etc. If you're reporting a problem with a specific version of a library in this repo, please check whether the problem has been fixed on main brach.
v3.10.40.1
iOS

Steps to reproduce.
Describe exactly how to reproduce the error. Include a code sample if applicable.
We are not able to reproduce the issue from our end.
We are seeing an issue where in the telemetry for the user is dropped completely for 3hrs. We see the telemetry in other telemetry flow.

Before dropping of the telemetry, there is bad network event shown and we change set the transmit profile to BestEffort at this time.

Is there any reason of dropping telemetry. I understand that the cadence of upload is changed. But will it drop events? And how do we get any callbacks in case the events are dropped?

From the telemetry, at 23:07:56Z Lan opened the pre-join screen for a meeting (preJoin_preJoin_view), joined at 23:07:58Z (join_scheduled_meetup, view_meetingJoinedSuccessfully_view), and put the call into PIP mode at 23:08:07Z (DisplayPIP_meeting_tap_PIPInForeground).

At 23:09:49Z, a bad network event fired (badNetworkBanner_banner_badNetworkBanner), indicating the network went offline while the app was in the background with the call in PIP.

The last event from her device was at 23:10:13Z (OPVideoPlayer), after which there are zero events for over 4 hours.

What is the expected behavior?
What did you expect to see?
No telemetry should be dropped.

What is the actual behavior?
What did you see instead?
Telemetry was dropped.

Additional context.
Add any other context about the problem here.