# Q2 2026 patches > [!TIP] > > 📅 Released: 5 June, 2026 | Apteco software | Build version numbers | | --- | --- | | Apteco FastStats Server | 5.9.6 | | Apteco FastStats | 1.1.26110 | | Apteco PeopleStage | 1.0.26110 | | FastStats Designer | 1.3.26110 | | Web Service | 1.1.26110 | | FastStats Service | 1.3.26110 | | Digital Integration | 1.0.26110 | > [!NOTE] > > **Info** > > For instructions on applying patches, see [Applying patches](). ## Patch 10: CLM jobs now retry correctly after a deadlock on non-English SQL Server locales *15 October, 2026* FastStats Service We've fixed an issue where campaign lifecycle management jobs failed instead of automatically retrying after a temporary SQL Server deadlock, on SQL Server instances configured for a non-English locale. Deadlocks are now detected using the underlying SQL error code, so retries work correctly regardless of locale. To apply this fix: 1. Install the FastStats Configurator version 1.3.26110.28 or later contained within the [WebService.zip]() file. 2. Use the FastStats Configurator to upgrade the FastStats Service to version 1.3.26110.45 or later. --- ## Patch 9: Apteco Email gateway timeouts *1 September, 2026* FastStats Service Digital Integration We've fixed an issue where Apteco Email could fail with gateway timeouts. The system now retries requests for up to 60 seconds so email operations complete successfully. To apply this fix: 1. Install the FastStats Configurator version 1.3.26110.28 or later contained within the [WebService.zip]() file. 2. Use the FastStats Configurator to upgrade the FastStats Service to version 1.3.26110.45 or later. 3. Install the FastStats Email Response Gatherer version 1.0.26110.25 or later contained within the [DigitalIntegration.zip]() file. --- ## Patch 8: Uploading multiple match columns to Google Ads *1 September, 2026* FastStats Service Digital Integration We've fixed an issue where uploading an audience to Google Ads with more than one match column incorrectly combined them into a single match. This caused the upload to find no matches. We've also extended the match process to correctly batch audience uploads that exceed Google's maximum of 100,000 entities. To apply this fix: 1. Install the FastStats Configurator version 1.3.26110.28 or later contained within the [WebService.zip]() file. 2. Use the FastStats Configurator to upgrade the FastStats Service to version 1.3.26110.45 or later. 3. Install the FastStats Google Response Gatherer version 1.0.26110.24 or later contained within the [DigitalIntegration.zip]() file. --- ## Patch 7: CheckPoint MaximumId processing fixed for large identity values *1 September, 2026* FastStats Service We've fixed an issue where checkpoints exceeding the maximum int value failed to record, which affected staging database updates. Checkpoint processing now uses bigint instead of int. To apply this fix: 1. Install the FastStats Configurator version 1.3.26110.28 or later contained within the [WebService.zip]() file. 2. Use the FastStats Configurator to upgrade the FastStats Service to version 1.3.26110.45 or later. --- ## Patch 6: FastStats Server optimisation and count accuracy fixes *27 August, 2026* FastStats Service FastStats Designer We've fixed several issues that could cause FastStats to return incorrect counts, or crash, in specific scenarios: - Counts could be incorrect the first time a query ran, correcting themselves on subsequent runs - A crash could occur when running a query with more than 1,000 selections - With query optimisation enabled, counts could be incorrect for a selection based on a date rule, an indirect variable, or a variable stored in-memory To apply this fix: 1. Install the FastStats Configurator version 1.3.26110.28 or later contained within the [WebService.zip]() file. 2. Use the FastStats Configurator to upgrade the FastStats Service to version 1.3.26110.45 or later. 3. Use the FastStats Configurator to upgrade the FastStats Binaries to version 1.1.26110.43 or later. > **Note** > > FastStats Local users need to install version 1.1.26110.43 or later, contained within the [FastStatsLocal.zip]() file. 4. Install FastStats Designer version 1.3.26110.31 or later contained within the [Designer.zip]() file. --- ## Patch 5: SMS sends failing due to null values in message payloads *5 August, 2026* Digital Integration We've fixed an issue where sending an SMS could fail with an error. JSON serialisation didn't correctly handle null values in the message payload, which caused the failure. To apply this fix: 1. Install the FastStats Email Response Gatherer version 1.0.26110.22 or later contained within the [DigitalIntegration.zip]() file. --- ## Patch 4: Application files blocked by Windows Defender *5 August, 2026* We've fixed an issue where some application files weren't code signed by Apteco, which could cause Windows Defender SmartScreen to block their installation. All application files are now code signed. If you haven't experienced this issue, you don't need to do anything. If Windows Defender SmartScreen blocks one of your Apteco application files, download the latest version of the affected component from the [Software Releases]() portal, then reinstall it. See [Applying patches]() for instructions. --- ## Patch 3: Expression editor error in German locale *5 August, 2026* FastStats We've fixed an issue where opening an expression while running FastStats in German locale returned an XML validation error. This prevented the expression editor from loading. To apply this fix: 1. Install the FastStats Configurator version 1.3.26110.25 or later contained within the [WebService.zip]() file. 2. Use the FastStats Configurator to upgrade the FastStats Binaries to version 1.1.26110.41 or later. > **Note** > > FastStats Local users need to install version 1.1.26110.41 or later, contained within the [FastStatsLocal.zip]() file. --- ## Patch 2: BinaryDictionary memory allocation with text keys *5 August, 2026* Designer We've fixed an issue where building a system with text keys in Designer created temporary files far larger than necessary. File size scaled with both the number of records and the key size, increasing temporary disk space usage and affecting performance during the build. Temporary file size now scales with the number of records only. To apply this fix: 1. Install FastStats Designer version 1.3.26110.29 or later contained within the [Designer.zip]() file. --- ## Patch 1: Distributed processing cube cache *11 June, 2026* FastStats Service We've fixed an issue where cube queries could return an error when you enabled distributed processing. If a cube fails to run in a distributed manner, the system now falls back to running the query sequentially, rather than returning an error. This improves the reliability of systems that use distributed processing. To apply this fix: 1. Install the FastStats Configurator version 1.3.26110.21 or later contained within the [WebService.zip]() file. 2. Use the FastStats Configurator to upgrade the FastStats Service to version 1.3.26110.36 or later.