Skip to content

fix(contact-center): expose wellness session and route RTD notifications - #5251

Merged
bhabalan merged 6 commits into
webex:nextfrom
bhabalan:codex/wxcc-12423-wellness-session-snapshot
Sep 30, 2026
Merged

bhabalan merged 6 commits into
webex:nextfrom
bhabalan:codex/wxcc-12423-wellness-session-snapshot

Conversation

@bhabalan

@bhabalan bhabalan commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

COMPLETES # https://jira-eng-sjc12.cisco.com/jira/browse/WXCC-12423

This pull request addresses

After a page refresh, a host cannot recover the active wellness session from the profile returned by register() when registration silently restores a logged-in station. Wellness notifications can also arrive on the RTD WebSocket, but the SDK does not emit them to listeners of the existing WELLNESS_BREAK event. Both gaps affect the wellness widget flow in webex/widgets#741.

by making the following changes

  • Include the SDK-owned agentSessionId in the returned Profile when registration restores an active station session. Keep the field absent when no station session is active.
  • Connect the RTD WebSocket when wellness breaks are enabled, including when transcripts and suggested responses are disabled.
  • Validate and route wellness notifications from the RTD WebSocket through the existing WELLNESS_BREAK event. Continue to pass other RTD messages to TaskManager.
  • Update the Contact Center contract and module documentation, and add unit coverage for the new paths.

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios were tested

Vidcast: https://app.vidcast.io/share/aec5197c-5bbe-4d1a-b2f3-a193adb64853

  • yarn workspace @webex/contact-center test:unit — 1,228 tests passed. The unit coverage includes restored-session profile data, RTD connection for wellness-only agents, wellness event routing, and the non-wellness RTD path.
  • yarn workspace @webex/contact-center test:style — 0 errors and 41 existing warnings.
  • yarn workspace @webex/contact-center build:src — passed.

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • GAI was used to create a draft that was subsequently customized or modified
  • Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Github Copilot
    • Other - OpenAI Codex
  • This PR is related to
    • Feature
    • Defect fix
    • Tech Debt
    • Automation

The AI-assisted changes were reviewed against the SDK source, tests, and contract documentation. Existing copyright annotations were retained.

I certified that

  • I have read and followed contributing guidelines
  • I discussed changes with code owners prior to submitting this pull request
  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the documentation accordingly

Make sure to have followed the contributing guidelines before submitting.

@bhabalan
bhabalan requested a review from a team as a code owner September 28, 2026 16:02
@bhabalan bhabalan added the validated If the pull request is validated for automation. label Sep 30, 2026
@github-actions github-actions Bot removed the validated If the pull request is validated for automation. label Sep 30, 2026
@bhabalan bhabalan added the validated If the pull request is validated for automation. label Sep 30, 2026
@bhabalan
bhabalan merged commit c622eb6 into webex:next Sep 30, 2026
10 checks passed
@github-actions

Copy link
Copy Markdown
🎉 Your changes are now available!
Released in: v3.12.0-next.220
📖 View full changelog →
Packages Updated Version
webex 3.12.0-next.220
@webex/contact-center 3.12.0-next.133

Thank you for your contribution!
🤖 This is an automated message. For queries, please contact support.

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

Labels

validated If the pull request is validated for automation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants