15h • General discussion
Look for Dependents Before You Delete
Command note: Deleting is easy. Finding out what depended on it is the expensive part.
Lesson learned: we once removed a tag we thought was dead. Two workflows still keyed off it, and both quietly stopped firing. Nothing errored. We noticed a week later when follow-ups went missing.
The rule: nothing gets deleted until you know what points at it.
What quietly depends on other things:
• Tags that trigger or filter workflows
• Custom fields used in templates and merge fields
• Pipeline stages referenced by automations
• Trigger links and forms that feed a workflow
• Calendars tied to booking confirmations
Do it now:
1) List what you plan to delete — one line each
2) Search every workflow, template, and smart list for each name
3) Write down every hit and who owns it
4) Repoint or retire those dependents first
5) Archive or rename before you delete, then wait a week
6) Delete only when nothing has complained
A deleted item never sends an error. It just stops doing its job.
0
0 comments
Look for Dependents Before You Delete
Suggested communities
Powered by