BUG - Sev-3 - All - Secure Messaging: Inbox displaying as empty on pages that are past 100 messages

[rbontrager]

What happened?

The inbox is coming in as empty when you use pagination to go to a page past 100 messages.

Specs:

• Device:
• OS:
• User Account:
• Accessibility State:

Steps to Reproduce

1. Login to user +226 (or any user with over 100 messages)
2. Using the next page feature go to the inbox for messages 101-110. Notice that the inbox is coming back as empty when it isn't.

Desired behavior

Acceptance Criteria

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See Bug Tracking for details on severity levels

• Impact: High Low
• Frequency: High Low

• 3 - Low
• 2 - High
• 1 - Critical

Linked to Story

Screen shot(s) and additional information

Full JSON response for services related to issue (expand/collapse)

Ticket Checklist

• Steps to reproduce are defined
• Desired behavior is added
• Labels added (front-end, back-end, global, Health, relevant feature, accessibility, etc)
• Estimate of 1 added (for front-end tickets)
• Added either to the relevant feature epic (if found during new feature implementation), or the relevant team's bug epic (Global, Health & Benefits, API, QART)

[alexandec]

The issue is that we are attempting to fetch 5000 messages:

GET /mobile/v0/messaging/health/folders/0/messages?page=1&per_page=5000&useCache=false

However, we are actually limited to 100 messages based on how the endpoint is implemented. 100 is the max we can receive with a single call.

Looks like the issue started in May with the React Query migration of Secure Messaging endpoints. What we used to do before that was:

return get<SecureMessagingFolderMessagesGetData>(`/v0/messaging/health/folders/${folderID}/messages`, {
  page: page.toString(),
  per_page: DEFAULT_PAGE_SIZE.toString(),
} as Params)

so we only fetched messages 10 at a time, and fetched 10 more as the user moved to the next page. We could potentially return to that form of user-initiated fetching in order to resolve the issue.

Additional notes:

• Demo mode, and possibly unit/E2E tests, would need to be updated accordingly.
• The same issue probably occurs with other folders, not just the inbox.

Slack thread: https://adhoc.slack.com/archives/C067S0FRP0C/p1734027121247159