Unattended automation is automation that runs entirely on its own, with no person watching or stepping in. It usually fires on a schedule or a trigger, does its work in the background, and finishes without anyone touching it. The classic example is a robot that processes invoices overnight, so the queue is clear before anyone arrives in the morning.
Think of a dishwasher running while you sleep. You load it, press start, and the machine handles the whole cycle in the dark while the house is quiet. You only check it in the morning. Unattended automation works the same way, often as a software robot on a server, and is frequently set off by a scheduled job at a fixed time.
The opposite approach keeps a human in the loop, which is attended automation, used when judgement or oversight is needed. Unattended is the right fit for high-volume, rules-based work that does not need a human decision. The trade-off is that you must invest in solid logging and alerting, because nobody is there to catch a problem live.
One quiet danger is silent failure. If a bank changes its login page, a nightly bot might fail every run for a week before anyone notices, and by then a backlog has piled up. That is why a good build does not just log success; it raises an alarm on a missed run, so silence never gets mistaken for everything working. A common safeguard is a heartbeat check that expects the job to report in on time and shouts if it goes quiet.
At TopDevs we design unattended automations with monitoring baked in, so a client’s overnight processes run quietly and someone is told straight away if a run needs attention.
