Skip to content

chore(pla-1906): update message status condition docs to mention retention enforcement #1210

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 7, 2025
Merged

chore(pla-1906): update message status condition docs to mention retention enforcement #1210

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions content/designing-workflows/step-conditions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

<Callout
Expand Down
Loading