Release highlights

New helper text when Call Targets or Scheduler templates cannot be deleted.

Call Targets and Scheduler templates cannot be deleted when a Scheduler widget or Intent is associated with them, but previously users had no indication of why the Delete button was grayed out for these items.

We have added helper text that appears when hovering over a grayed out Delete button that clearly communicates why the Call Target or template cannot be deleted. For Call Targets, the name of the associated widget or Intent is listed in the helper text.

Security enhancements

We continue to introduce security enhancements to address emerging trends and incorporate industry standard best practices.

Resolved issues

We have resolved an issue causing false positive responses from the Agent Answer API.

Some requests to the Invoke an Agent Answer endpoint were returning a successful 202 response, even though the answer events were not successful. We have identified and resolved the underlying cause to ensure that success responses are only returned for successful outcomes.

The Call Target filter on the Callback Overview and Callback Status pages now functions correctly when the page is loading.

Due to an issue with the timing of filter processing, the Call Target filter was not applied to the Callback Overview or Callback Status pages while they were loading data. We have adjusted the underlying logic to ensure that the filter is applied whenever it is used.

Reverting custom media changes for custom metadata media now works as expected.

After uploading an audio file to a Media Set for custom metadata media, clicking the Undo Custom Prompt Changes button could result in an error and a failure to remove the audio file. The cause of the potential error has been resolved in this release.

A cause of slow responses by the Scheduler API has been resolved.

Initial responses to the Request Status of All Widgets endpoint of the Scheduler API were taking up to 10 seconds, while subsequent responses were much quicker. We have addressed the underlying cause to ensure that the initial response is returned within three seconds. This issue mostly affected organizations with a large number of widgets.

Drill-down menus on the Messaging Usage dashboard are working once again.

Recently, the Avg Messages Per Customer drill-down menu on the Messaging Usage Insights dashboard were not populating data.

Two issues with exports of the Call Detail report have been resolved:

• The Outcome column was empty for all calls, and now includes data as expected.

• Some values in the "Has Retry" column were boolean, while others were integers. All values are now boolean (True/False).

On the Callback Status page, the Calls in Queue/Max and Active Calls/Max columns no longer show an infinite maximum when the First Party column is removed.

Removing the First Party column previously caused of the value of Max Queue Depth and Max Active Calls not to be recognized on the Callback Status page.

Callback requests via API will now show an appropriate error if the associated Call Target has recently been deleted.

Previously, sending a request to the Register a Callback endpoint shortly after deleting the associated Call Target would return a success response, even though no callback could actually be processed. A 400 Bad Request error will now be returned in this scenario.

Changes to the Scheduler HTML template can be saved once again.

We recently found that changes made to Scheduler templates on the Edit Template HTML page could not be saved if any style attributes were changed. With this release, template changes can be saved as expected.