Do not stack too many jobs on one automation

It is tempting to keep adding tasks to an automation that already works — one more condition, one more notification, one more connected tool. Over time this turns a simple process into a tangled one that nobody fully understands anymore.

This matters because every added job increases the number of ways the whole thing can fail, and it makes each failure harder to diagnose since you are no longer sure which of many jobs actually broke. A tangled automation also becomes something people are afraid to touch, which means small fixes get delayed because nobody wants to risk breaking everything else bundled inside it. Keeping each automation focused on one clear job keeps it easy to understand and safe to change. I've watched a simple automation turn into something nobody wanted to touch after one too many conditions got bolted onto it.

If an automation has grown to handle several unrelated jobs, that is usually a sign it needs to be split apart.

Try this today: count how many separate jobs your busiest automation actually handles, and consider splitting off the one that fits least.