AFI
Date is not on
Date is not on is the inverse of Date is on. It passes when the date in the field falls on any calendar day other than the one you type.
When to use it
Use it to carve one day out of an otherwise general rule: skipping a blackout date, excluding a public holiday from a scheduling workflow, or holding back submissions dated on a day you handle manually.
How to configure it
- Open AFI → Integrations and edit your integration.
- Switch on Conditional Logic.
- Pick the date field, choose Date is not on, and type the day you want to exclude.
How it behaves
Both sides are parsed and reduced to a plain calendar day before comparison, so the time of day plays no part. A submission at any hour of the excluded day fails the rule.
Relative phrases work, so today excludes the current day and stays correct over time.
If either side cannot be read as a date, the rule fails and the integration does not run. Note what this means in practice: a submission with a blank or unparseable date does not pass Date is not on, even though it is technically “not on” that day. The operator only passes for dates it can actually read.
Dates are interpreted in your WordPress site’s timezone.
Example
A support desk closes on 25 December. Tickets dated that day are triaged by hand rather than pushed into the usual routing integration.
Set the rule to {{ticket_date}} Date is not on 2026-12-25.
Notes
To exclude more than one day, add a rule per day and set the match mode to all, so a submission must miss every excluded date to pass. See Must match condition (all / any).