fix: busy/not-answered calls stay in agent worklist after call closure#135
Conversation
When a call is closed with a not-answered reason (Number busy, Switched off, No reply, etc.), the call was being unallocated from the agent due to isCallDisconnected being forced true. This fix restores the agent allocation so the record stays visible in the agent's worklist for retry. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Roshini's change unallocated ALL disconnected calls including busy ones. Fixed at root cause - unallocation now skipped when reason is a not-answered type (busy, switched off, no reply etc). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|



📋 Description
JIRA ID: AMM-2315
Please provide a summary of the change and the motivation behind it. Include relevant context and details.
Summary
"Switched off" etc., the record was disappearing from their worklist.
unconditionally, including busy/not-answered ones.
reasonForCallNotAnsweredisa not-answered reason (busy, switched off, no reply, etc.).
Changes
CallClosureImpl.java: Added condition in disconnected block —unallocation only happens when reason is NOT a busy/not-answered type.
(no longer needed after fixing root cause).
Test Plan
✅ Type of Change
ℹ️ Additional Information
Please describe how the changes were tested, and include any relevant screenshots, logs, or other information that provides additional context.