Skip to content

[Due for payment 2026-08-05] feat: derive report-load skeleton gates from the request queue #96486

Closed

Description

@mountiny

Problem

The initial report-load skeleton on several report surfaces reads the stored isLoadingInitialReportActions flag. Like other stored loading flags, it is a shadow of the request queue and can be stranded by a reload or dropped response, leaving the skeleton up with no request running.

Solution

Move clean, screen-level consumers onto the queue-derived, per-report useIsReportLoadPending(reportID) hook, which reads whether an OpenReport request for that report is currently in the SequentialQueue. Extend the hook to accept reportID: string | undefined. Migrated: MoneyReportHeaderNextStep, MoneyRequestReportView, ReportFooter. The flag and its writers are untouched for a separate removal PR.

PR

#96395

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    ReviewingHas a PR in review
    InternalRequires API changes or must be handled by Expensify staff
    on Jul 20, 2026
  2. changed the title [-]feat: derive report-load skeleton gates from the request queue[/-] [+][Due for payment 2026-08-05] feat: derive report-load skeleton gates from the request queue[/+] on Jul 29, 2026
  3. melvin-bot commented on Jul 29, 2026

    @melvin-bot

    @DylanDylann

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.45-14 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-05. 🎊

    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]

  4. 5 remaining items

  5. melvin-bot commented on Aug 4, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  6. melvin-bot commented on Aug 4, 2026

    @melvin-bot

    @mallenexpensify Eep! 4 days overdue now. Issues have feelings too...

  7. DylanDylann commented on Aug 5, 2026

    @DylanDylann
    Contributor

    perf improvement. This doesn't require the checklist

  8. mallenexpensify commented on Aug 7, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @DylanDylann due $250 via NewDot

  9. quinthar commented on Sep 26, 2026

    @quinthar
    Contributor

    Approved $250 to @DylanDylann

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2InternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions