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
[Due for payment 2026-08-27] Lazy-load contact options: shell first, createOption after getValidOptions #97788
On large accounts, the contact option list is built eagerly: a full createOption is constructed for every personal detail, which pulls in policy, tag, and archive lookups plus icon building. Most of those options are then thrown away by filtering and top-N ranking, so the bulk of that work is wasted and shows up as a long blocking cost in flows like ParticipantSearchResults / createFilteredOptionList.
Solution
Adds an opt-in lazyContactOptions path for flows that run contacts through getValidOptions. Contacts are first built as lightweight shells via createLazyContactOption (only the fields needed to filter and rank — text, login, accountID, participantsList), with policy/tag/archive lookups and the full createOption work deferred into buildFullOption. getValidOptions then hydrates only the contacts that survive top-N selection via hydrateLazyContactOptions, so full option work happens once per visible match instead of once per contact. useSearchSelector enables the flag; all other callers keep the eager behavior. Measured createFilteredOptionList improvement: ~900ms → ~700ms.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.56-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-08-27. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
Activity
melvin-bot commentedon Aug 7, 2026
@shubham1206agra Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
shubham1206agra commentedon Aug 8, 2026
PR in draft
melvin-bot commentedon Aug 11, 2026
@shubham1206agra Whoops! This issue is 2 days overdue. Let's get this updated quick!
9 remaining items
melvin-bot commentedon Aug 20, 2026
@shubham1206agra
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.56-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-08-27. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
melvin-bot commentedon Aug 26, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Aug 26, 2026
Payment Summary
Resolving PRs:
Lazy-load contact options: shell first, createOption after getValidOptions #97087
Reviewer: @shubham1206agra owed $250 via NewDot
Contributor: @staszekscp does not require payment (Contractor)
Contributor: @jmgraa does not require payment (Contractor)
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Aug 27, 2026
No review checklist from @shubham1206agra so I'm assuming payment isn't due, comment/reopen if ya disagree