Keeping them working.
WHY MAINTENANCE IS NECESSARY
Connected systems change, and automations built once decay.
WHAT CHANGES BREAK THEM
System updates altering interfaces Fields renamed or removed Credentials expiring Processes changing Platforms changing their limits or pricing
WHAT TO ESTABLISH
A record of every automation.
WHAT IT SHOULD CONTAIN
What it does What triggers it What systems it touches What account it uses Who owns it What happens if it fails
WHY WHO OWNS IT
Unowned automations are maintained by nobody.
WHAT TO REVIEW PERIODICALLY
Whether each is still needed Whether it still works Whether the process it supports has changed
WHY STILL NEEDED
Processes are discontinued and the automations run on.
WHAT TO CHECK
That outputs are actually appearing.
WHAT TO DO ABOUT AUTOMATIONS NOBODY UNDERSTANDS
Document them, or replace them.
WHY
They cannot be safely changed otherwise.
WHAT TO DO WHEN A PROCESS CHANGES
Update the automation as part of the change.
WHY AS PART OF IT
Updating afterwards does not happen.
WHAT TO TEST AFTER ANY CHANGE
The whole flow, not only the part changed.
WHAT TO KEEP
A way to perform the task manually.
WHAT TO ESTABLISH
That someone other than the builder can maintain it.
WHY
Otherwise the automation is a dependency on one person.
