--- title: "1926 Release - 2019-07-15" date: "2025-09-12T05:57:24+00:00" summary: "Discover key updates in AgilOne's 1926 release, including UI improvements, connector enhancements, and security upgrades." image: type: "announcement" url: "/customer-data-platform/release/2019-07-15/79786-1926-release-2019-07-15" id: "821d4ed1-e637-4fbf-ba55-67c545ea289b" --- **Area** **AgilOne JIRA** **Description of functionality after the fix** 360 Profiles AGO-9895 In the 360 Profiles application you can now adjust how many transactions and/or events are returned for you to view. The previous limit was 40, but now you can adjust this to be 25, 50, 75, or 100. Actions AGO-12127 We have significantly improved the performance of the Actions user interface by investigating and refactoring the largest performance bottleneck. We hope you enjoy the renewed Actions experience! Actions AGO-12261 Actions users will be happy to hear that (nearly) all filters now have improved descriptions and names. Additionally, we have hidden several duplicate filters that were confusing users. Platform: Cheetahmail Input Connector AGO-12310 For clients that use CheetahMail and have significant data volumes we have implemented an enhancement that will allow AgilOne to ingest this data. Previously we were exiting the data pull after an hour, but now we will attempt to pull data for at least 12 hours before we assume that the data pull is stuck and therefore can be killed. Platform: Google Ads Offline Conversions Output Connector AGO-12249 We are no longer failing the Google Ads Offline Conversions Output Connector when a partial data failure is returned by the Google Ads API. We are now logging any records that result in a partial data failure, and allowing the rest of the process to succeed. Settings: Users List AGO-12191 We have made a key security enhancement to the Settings Users listing page that will allow us to start providing access to super users. This page allows specific AgilOne users to review who has access to their AgilOne environment. There is an issue outstanding: disabled users are not currently identified as disabled. We hope to fix this soon, but in the meantime users might be confused by long-ago disabled users appearing to have access to their environment. In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.