You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Control Execution Frequency of recheckConnection() #77806
Control Execution Frequency of recheckConnection()
Background
The Expensify app performs connectivity checks using Ping requests to verify network availability and resume pending actions after transitions between online and offline states. These checks are initiated when the device’s connection state changes and when pending requests exceed their timeout thresholds.
Users frequently move between WiFi, mobile data, throttled bandwidth, and offline states, especially in areas with weak or fluctuating coverage. Sentry data indicates a significant increase in connectivity-related events over recent weeks, reflecting more frequent transitions that activate connection-monitoring logic. Several parts of the app depend on these signals to resume normal activity after disconnection, and these transitions occur regularly in real-world mobile environments.
Problem
When a user’s network connection rapidly fluctuates, if the app triggers connectivity checks in quick succession, then excessive Ping requests accumulate and slow the user’s ability to resume actions after reconnecting.
Solution
Update recheckConnection() to limit how often it runs and to ensure only one instance executes at a time. When the function is already running or was triggered too recently, subsequent calls are ignored.
By preventing rapid, overlapping connectivity checks during unstable network conditions, the app avoids accumulating Ping requests and can reliably resume user actions once the connection stabilizes.
Activity
melvin-bot commentedon Dec 16, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Krishna2323 (
External)melvin-bot commentedon Dec 16, 2025
Triggered auto assignment to @RachCHopkins (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Dec 16, 2025
Triggered auto assignment to @NikkiWines (
AutoAssignerNewDotQuality)3 remaining items
CosminStreteaCS commentedon Dec 23, 2025
I will be out of office during 24/12/2025 – 01/01/2026 and can take over any new updates or follow-ups after I’m back.
Krishna2323 commentedon Jan 6, 2026
@RachCHopkins the PR was deployed to production two weeks ago, so this one is ready for the payment summary.
@NikkiWines I don’t think we need a checklist here—do we?
NikkiWines commentedon Jan 6, 2026
Yeah I think we're fine without the checklist here
RachCHopkins commentedon Jan 13, 2026
This is the regular $250 I assume @NikkiWines?
NikkiWines commentedon Jan 14, 2026
yep, I believe so but cc: @mountiny as you created this issue
mountiny commentedon Jan 14, 2026
No need for checklist and $250
RachCHopkins commentedon Jan 15, 2026
Switching to Daily - will tackle this tomorrow
RachCHopkins commentedon Jan 16, 2026
Payment Summary:
No Upwork job.
🟢 to @Krishna2323 to request payment.
Krishna2323 commentedon Jan 17, 2026
Requested in ND.
twisterdotcom commentedon Jan 18, 2026
@Krishna2323 has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-1443-aee9-8e36-590a73a19074