From 6d9b84a725712be53c8533c23c394050e954fc28 Mon Sep 17 00:00:00 2001 From: Billy Ceskavich Date: Thu, 6 Nov 2025 15:34:19 -0500 Subject: [PATCH] chore(pla-1906): update message status condition docs to mention retention enforcement --- content/designing-workflows/step-conditions.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/designing-workflows/step-conditions.mdx b/content/designing-workflows/step-conditions.mdx index 807c67998..783e467d5 100644 --- a/content/designing-workflows/step-conditions.mdx +++ b/content/designing-workflows/step-conditions.mdx @@ -45,6 +45,8 @@ Message status conditions allow you to build a check for one workflow step that - An asserting (`"has"`) or negating (`"has not"`) condition operator. - The expected delivery or engagement status case. +Message state used to evaluate status conditions is subject to the Knock data retention policy. If you attempt to evaluate a status condition against a message that has expired out of your account's retention window, the condition will always evaluate to a false result. For more information, see our [data retention docs](/manage-your-account/data-retention). + ### Status cases