[syedanas-n]

Bug description

Bug 1031629: Doctor Non-Working Hours Not Displayed on Selection Until View Refresh

Root cause

The issue where scheduler appointments were intermittently not rendered after selecting a specialist was caused by a race condition between layout reinitialization and event rendering, triggered by an unconditional full scheduler refresh during dynamic updates.
In the existing implementation, the refreshDataSource method updates multiple scheduler‑level properties in a single execution flow, including WorkDays, resource filtering, working hours, and the event data source. These updates implicitly trigger an internal layout recalculation in the scheduler.

To address the missing events, the initial fix introduced a delayed full refresh:

await Task.Delay(50);
await scheduleObj.RefreshAsync();

It works fine in local, but fails in tunnel and staging.

Solution description

Calling RefreshAsync(false) resolves the race condition - LightWeight rerender

Code Studio usage(Mandatory)

• Code Studio used in this PR/MR?

  • Yes
  • No

• If Yes: Primary use (choose one)

  • Generate new code
  • Refactor/improve existing code
  • Tests
  • Bug fix / debugging help
  • Docs / comments
  • Review assistance (explanations/summaries)
  • Other:

• Outcome

  • Saved time
  • Neutral
  • Cost time

• If “Cost time” explain in short (1 or 2 lines):

Impact assessment

• Low - Affects a single feature with minimal user impact
• Medium - Medium level impact.
• High - Critical functionality or significant user impact

Reason for not identifying earlier

This issue was not identified earlier as it is dependent on asynchronous timing and environment‑specific rendering behavior. The initial fix appeared stable in local testing but failed under tunnel and staging conditions due to differences in render and communication latency.

Areas tested against this fix

• Verified scheduler event rendering after switching specialists, ensuring appointments are consistently displayed without requiring a manual refresh.
• Tested dynamic updates to WorkDays, working hours, and event data while switching doctors to confirm correct layout and event synchronization.
• Validated behavior across different environments, including local, tunnel, and staging setups, to ensure the fix is not timing‑ or latency‑dependent.
• Performed window resize and responsive layout checks to confirm that event rendering remains stable and does not depend on forced reflows or browser resize actions.

Breaking changes

• Yes (Tag breaking-issue)
• No

If yes, provide breaking commit details link and migration guidance.

Regression testing

• Verified fix doesn't reintroduce previous bugs
• Checked edge cases and error scenarios

Action taken to prevent recurrence

• Added/updated unit tests
• Other (specify): _________________
• NA

Automation status

• BUnit (provide PR link: _________________)
• Playwight (provide PR link: _________________)
• NA

Cross-platform verification

• Blazor Server
• Blazor WASM
• NA

Related issues

Is this issue present in EJ2 or other components?

• Resolved in EJ2 (PR link: _________________)
• Created task for EJ2 (Task link: _________________)
• Needs attention in other components (tag needs-attention-coreteam)
• NA

Output screenshots

Before:
https://github.com/user-attachments/assets/ed4c153b-d2df-49f1-bb22-47c7a7e837bc

After:
https://github.com/user-attachments/assets/d190cfae-1426-49ec-9b40-4e4304307b13

API changes

• New API added (API Review task link: _________________)
• Existing API renamed/modified (API Review task link: _________________)
• No API changes

Performance verification

• Verified no memory leaks introduced
• Verified no performance degradation
• Not applicable

Reviewer Checklist

• Reviewed the provided Code Studio usages related information.
• Code changes follow component guidelines
• All provided information reviewed and verified
• Solution addresses the root cause effectively