Maintain legacy automation rules
Review existing rules and avoid duplicate sends when introducing workflows.
Before changing a rule
Open Automation → Legacy Automations with the required access. Record which source event, template, recipient mapping, and variables the existing rule uses.
Review and migrate deliberately
- Inspect the current rule and its active state.
- Confirm the selected Meta template is approved and synchronized.
- Check trigger filters, recipient field, and parameter mapping against a real sanitized source event.
- Test with a controlled recipient and check the actual delivery result.
- If replacing it with a workflow, configure and test the replacement first, then prevent both mechanisms from handling the same production event.
Expected result and troubleshooting
One intended automation handles the event. If a customer receives duplicate notifications, inspect legacy rules, workflows, and source-system retries together. Do not delete a working rule until its dependencies and replacement are understood.