Product Update - Minor Update to v6.10.0
This is a minor update that includes the following bug fixes and changes.
Release Date
The date of release will be communicated separately over an email.
Summary
- WhatsApp User Preferences
- New WhatsApp Error Code
- Default Webex Connect Branded Domain for Link Shortening
- Event Scheduler Execution TPS limits
Details
Added –WhatsApp User Preferences
We've introduced real-time webhook notifications for businesses to know when WhatsApp users opt in or out of
marketing messages. You can subscribe to the ‘User Preferences’ event under Outbound Webhooks to receive these
updates. Marketing messages sent to users who have opted out will receive a failed Delivery Receipt (DR) showing status code 7876 and the description ‘User has stopped receipt of marketing messages.’ This DR will be sent via Outbound Webhooks, Notify URLs, and Data Streams when configured, and can also be viewed in Export logs, Debug logs, and Reports. Please note that businesses are allowed to send marketing messages only to WhatsApp users who have consented to receiving such messages, and this consent can be obtained through channels outside of WhatsApp as mentioned in this chapter: Getting Opt-ins.
Added – New WhatsApp Error Code
When businesses attempt to send marketing messages on WhatsApp to users who have opted out, the message will fail with a failed Delivery Receipt (DR) showing status code 7876 and the description “User has stopped receipt of marketing messages.” This DR will be sent via Outbound Webhooks, Notify URLs, and Data Streams when configured, and can also be viewed in Export logs, Debug logs, and Reports.
Added – Default Webex Connect Branded Domain for Link Shortening
In continuation to the link shortening enhancements introduced in the previous releases, we are now making a default Webex Connect Branded Domain available for use with the link shortening feature in the Messaging APIs. This enables users to utilize shortened URLs without any domain provisioning dependencies. Please note that the default domain may vary by region. For more details and region-specific information, refer to the Shortened URLs documentation in the Help portal.
Changed – Event Scheduler Execution TPS limits
Event Scheduler now supports higher message throughput. You can now configure Execution TPS of up to 300 TPS at the Schedule level, an increase from the previous maximum of 50 TPS. Please note that this remains subject to tenant-level TPS limits and the available throughput at any given time.
Important Additional Notes
- Upcoming Legacy SDKs Deprecation Deadline - We highly recommended you to upgrade to the latest modular
iOS and Android SDK, since the legacy iOS and Android SDKs will be deprecated on 20th August 2025.
Changelog
| Update | Description |
|---|---|
| Added | WhatsApp User Preferences |
| Added | New WhatsApp Error Code |
| Added | Default Webex Connect Branded Domain for Link Shortening |
| Changed | Event Scheduler Execution TPS limits |
| Fixed | Event Schedulers are not getting disabled or deleted, and event schedules are being triggered and executed even when the Tenant / Group / Team is deleted. |
| Fixed | For Email via SMTP, MESSAGE-ID header passed to Send Message API was being ignored. |
| Fixed | When names of inbound attachments contained special characters, they were causing issues with PCI and Malware scan. This is applicable only to Webex Connect tenants that are integrated with Webex CC or CCE. [INC1153764] |
| Fixed | When using the Link Shortener Prebuilt node, ‘Click’ notifications are not being sent to the configured Webhook URLs. |
| Fixed | Event Scheduler was incorrectly marking some records as duplicates when processing bulk uploads with large number of records, even though the file contained no duplicates. [INC1138388] |
| Fixed | Webex SSO users were unable to edit notification settings in the Profile Settings page without changing the username. |
| Fixed | Users were not able to share an asset with multiple Groups or Teams through the Share App functionality. |
| Fixed | Flows with comments exceeding 250 characters on the Make Live screen failed to publish. An inline error message has now been added to guide users to stay contained within the character limit. |
| Fixed | The HTTP Request, Data Parser, Custom, and Prebuilt Integration Nodes would stop processing all payload parameters if any parameter was invalid or missing. With this update, they now skip only the unavailable or invalid parameters, and continue to populate the valid ones, allowing the flow to execute with the available parameters. [INC1086017] |
| Fixed | Inline validation has been added to the Branch Node to prevent special characters in branch names, which previously caused failures during flow execution. |
| Fixed | Flow ‘Delete’ and ‘Export’ operations were failing for transactions in the month of July 2025. |
| Fixed | The Flow Outcome for AI Agent notifications did not allow passing payloads using only variables due to the JSON validation. This validation has been removed, enabling the use of variables alone as payload. Note - This change does not apply to the Azure environment. |