Twilio Changelog

Previously, segment samples did not refresh after initial segment creation (or after editing the conditions of a segment). With this release, segment samples are now refreshed hourly as long as Marketing Campaigns detects any changes as contacts enter or exit the segment. If no changes are detected, the next refresh will occur at 2 hours, and then 4, with a maximum delay to segment sample refresh of 24 hours.

For a real-time view of all contacts within your segment at any time, you can always export a CSV. This is not dependent on the sample refresh cadence.

For more information about the segment refresh cadence, see our segmentation documentation.

From the Contacts page, you can now see when the next scheduled segment will occur by hovering over the segment contact count. This same information can also be found on the segment detail page beneath the total contact count for that segment.

For a real-time view of all contacts within your segment at any time, you can always export a CSV. This is not dependent on the segment refresh cadence.

The sample refresh cadence has also been made available to Marketing Campaigns API users via the next_sample_update field.

This release of Flex UI introduces usability improvements for the Conversation Screen. Now when users drill down to individual conversations they stay natively in the Flex UI. The former Conversation Screen is still available but will be deprecated.

Other notable changes:

• The Teams View will now recover automatically from connection loss. Users will not need to refresh the page to recover their connection.
• Several dependency packages have been upgraded to patch security vulnerabilities.

For more details on this release, please visit the Flex UI release notes.

Following the release of Video Log Analyzer in Console, we have exposed a Video Log Analyzer API for retrieving Programmable Video Room and Participant details.

This resource allows developers to simplify troubleshooting and help identify commonalities in reported issues by programmatically retrieving critical metadata about Participant and Room behavior. The information provided includes: why a Participant left a Room, how the Room was ended, browser/operating system details, Participant error codes, and more.

For more information, see the docs.

Updating a Super SIM’s status to inactive now terminates any existing data sessions immediately and new connection attempts will be rejected. To resume using your Super SIM, change its status back to active to allow it to reconnect.

In TaskRouter, timestamps for TaskQueueEnteredDate will now provide millisecond precision. Although TaskQueueEnteredDate was already in the ISO8601 format yyyy-mm-ddThh:mm:ss.mmm, milliseconds were previously rounded to 000 in the event data.

To learn more about the TaskRouter Events resource, please refer to our documentation.

Voice Insights API responses have been updated to include edge location naming for Twilio's media and signaling edge.

Responses from the /Summary endpoint will include edge_location as part of the properties object; e.g. {carrier|client|sip}_edge.properties.edge_location. For Voice SDK calls it has also been added to {to.callee|from.caller}.sdk.edge_location.

Responses from the /Events and /Metrics endpoints will include edge_location as part of the edge metadata; e.g. {carrier|client|sip}_edge.metadata.edge_location. For Voice SDK Events it has also been added to sdk_edge.metadata.sdk.edge_location.

This information augments the deprecated region naming convention. For more information, see our docs.

Now you can easily search large Flows and jump to a specific widget in Studio. No more dragging and panning the canvas to find a widget!

To launch the search bar, click the magnifying glass or use the keyboard shortcut CMD + k for Mac and CTRL + k for Windows.

Type a partial name and select the widget from the search results to jump instantly to that widget.

Try it now in Studio!

Trunking Termination Calls per Second (CPS) refers to how many new SIP Trunking call setups are allowed in one second for Trunking Termination calls (outgoing traffic from your communications infrastructure to the PSTN). Twilio, by default, provides the ability for you to place 1 CPS per Trunk per Region (see limits).

With this release you are now able to set the Trunk CPS between 1 and 15 per region. This release will show the pricing changes as well. In addition, it is possible to schedule the effective date in advance when decreasing your Trunk CPS.

For details, please check our Trunk CPS documentation.

Verify’s push-based verification (authentication) channel has advanced from the Private Beta to the Public Beta release stage. With this release, the Push API and SDKs are now publicly available and ready to support production-scale workloads. Learn more about how Verify Push allows you to add a secure, cost-effective, and low-friction user verification feature into your Android or iOS mobile app, without requiring a phone number or email from your users.