# 1.177.0 - 15 April 2026 ### Release Overview This release focuses on improving platform reliability, performance, and overall usability. Alongside continued work behind the scenes to modernise infrastructure, we’ve made targeted updates to simplify the user experience and ensure more consistent, predictable behaviour across the platform. You’ll also see improvements to TXT field configuration and a more streamlined mailout setup experience, along with a range of performance, security, and stability enhancements. ### TXT fields now support default values TXT fields can now be configured with a default value of Yes, No, or None. This helps ensure contacts resolve to a known value even when no explicit preference has been set. Because setting a default value of “Yes” may have compliance implications (for example, treating contacts as opted in without an explicitly recorded consent), additional safeguards have been introduced. As shown in the screenshot below, when selecting “Yes” as the default, you’ll be required to review a clear warning and confirm your understanding before proceeding. This option is intended for use only where contacts have already provided explicit consent through a compliant process. The added confirmation step helps ensure this is used appropriately and with full awareness of the implications.

A confirmation message will show when you set a default value of Yes for a TXT field.

### Simplied mailout scheduling experience We’ve removed the “time-sensitive mailout” option from the mailout setup process. This option was not actively used and could create unnecessary complexity when configuring mailouts. Its removal helps streamline the experience, making it clearer and more straightforward to set up and manage both one-off and automated mailouts.
### Improvements and bug fixes We're constantly making small changes to ensure that, behind the scenes, everything will go as smoothly as possible and to continue to build a strong foundation to make improvements to the platform. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ubiquity.co.nz/releases/2026/1.177.0-15-april-2026.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.