Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Agents are unable to answer call



Third-party Callback Manager holds a user's position in the phone queue and connects the call. Agents are unable to answer the call when the Callback Manager attempts the connection. A latency of around 10k ms occurs. With the last execution, the Summary common to all latency displays the UpdateClipboard step for the Phone UI.

Error Messages

Unable to read updated Call Interaction for ID!xxxx

Steps to Reproduce


Root Cause

The error occurs because the Call ID objects are not purged from the Pega table through the purgecallobjects agent. The values for the agent must be customized to ensure that the old data is purged.
The out-of-the-box report has pagination enabled, hence adjustments must be made when more than 50 or more objects are cleared per execution.


  1. Apply HFix-39442.
  2. Enable the purgecallobjects agent. 


Published February 22, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us