How do I stop an automation from overspending?
Set Maximum cards per year on the rule to limit its yearly sends. Blank means no limit. The counter resets January 1. Each run also checks credits, do-not-mail entries and message fields before creating a card.
On this page
#Set a yearly limit
Open the rule’s settings and enter Maximum cards per year. Set it for the audience you expect, with room for new contacts if needed. The limit belongs to this rule; separate rules have separate limits.
| Reason | Action |
|---|---|
| Yearly limit reached | Raise the limit if the additional sends are intended. |
| Not enough credits | Add credits. Future runs can retry dates still inside the sending window. |
| Do-not-mail match | Keep the opt-out unless it is a mistake. |
| Missing merge value | Fill in the contact field, set a fallback where offered, or remove the field from the message. |
| Occurrence already handled | No action. This rule has already created the card for that date. |
#Check overlaps and event retries
Two rules can send to the same contact. Check their lists before turning them on. For inbound hooks, send an Idempotency-Key based on the source event and reuse it on retries. A reference value by itself is not duplicate protection.
#Pause a rule
Turn the rule off to stop future runs and keep its history. Deleting and recreating it gives the new rule its own occurrence history, so it could send to someone the old rule already covered. Pausing does not cancel existing cards.
Last checked against the product on . Something wrong or missing? Tell us.