Rules and schedules
Define when Anchor creates occurrences and how it follows up.
Rule behavior
A rule is the reusable definition for an Anchor notification. It controls the message, schedule, response requirement, retry policy, quiet-hours behavior, and actions available to the recipient.
Pausing a rule prevents future scheduled occurrences. Existing active occurrences continue until they reach a terminal state.
Scheduling
Schedules use the rule timezone. Anchor evaluates recurring schedules with daylight-saving transitions in mind and records the scheduled time for each occurrence.
Quiet hours delay delivery when the configured policy permits it. They do not silently discard an occurrence.
Manual and API triggers
Trigger now creates an occurrence using the same persisted workflow as a scheduled trigger. API clients can use POST /v1/rules/{rule_id}/trigger with an API key authorized for rules:trigger.
Duplicate a rule when you want a new independently editable definition with the same starting configuration.