diff --git a/content/change-logs/analytics/apama-in-c8y-20241104-Fixed-a-potential-deadlock-when-a-large-number-of-requests-are-waiting-to-be-flushed.md b/content/change-logs/analytics/apama-in-c8y-20241104-Fixed-a-potential-deadlock-when-a-large-number-of-requests-are-waiting-to-be-flushed.md
index 7cac7119cd..fa3a325812 100644
--- a/content/change-logs/analytics/apama-in-c8y-20241104-Fixed-a-potential-deadlock-when-a-large-number-of-requests-are-waiting-to-be-flushed.md
+++ b/content/change-logs/analytics/apama-in-c8y-20241104-Fixed-a-potential-deadlock-when-a-large-number-of-requests-are-waiting-to-be-flushed.md
@@ -1,5 +1,5 @@
 ---
-date:
+date: 2024-11-21
 title: Fixed a potential deadlock when a large number of requests are waiting to be flushed
 change_type:
   - value: change-VSkj2iV9m
@@ -12,6 +12,6 @@ build_artifact:
   - value: tc-KXXmo2SUR
     label: apama-in-c8y
 ticket: PAM-35075
-version: 25.298.0
+version: 25.311.0
 ---
 When using a large number of client connections with the `client.numClients` tenant option, there was a potential deadlock when a large number of requests were waiting to be flushed. This has been fixed.