Release notes for version 23.124 of Connect (Enhancement & Bug Fix)
Date of release
Summary
Enhancements to cache refreshing process to address "Apex CPU time limit exceeded" error
Enabled by default
Agent changes
In the previous version of Connect, agents were receiving the "Apex CPU time limit exceeded" error message. This message appeared when the cache size selected for the dial list was near the maximum cache size supported by Connect. This was due to Connect trying to refill the entire cache in a single transaction — the time to perform this transaction often exceeded the maximum Apex CPU time limit set by Salesforce.
In this release, Connect breaks down the cache refilling job into multiple transactions when the cache size selected for the dial list is more than 1000. This ensures that the agents do not receive the "Apex CPU time limit exceeded" error message.
Improved error handling when deleting dial lists
Enabled by default
Supervisor changes
In the previous version of Supervisor for Dial Lists, when a supervisor initiated the deletion of one or more dial lists, the related records were deleted by an asynchronous job. If one of the records encountered an error during the deletion process, the whole job was stopped, and the supervisor was not notified of the issue.
In this release, the dial list deletion job has been updated to handle individual failures without interrupting the entire deletion process. In case of a failure during record deletion, the supervisor who initiated the deletion will be notified by email about the status of the records, along with any error messages. This will enable the supervisor to take corrective action if needed.
For general assistance, please contact Customer Support.
For help using this documentation, please send an email to docs_feedback@vonage.com. We're happy to hear from you. Your contribution helps everyone at Vonage! Please include the name of the page in your email.