Can a business automation run when your computer is off?

Ask where every step runs

Yes, a workflow can run while your office computer is off if the services it needs are running elsewhere and none of its steps depends on that computer. A scheduled task on the office machine still needs that machine available. Adding AI does not change this dependency. Before buying after-hours automation, ask the implementer to draw the complete route from incoming information to the result your team receives. A scheduled start alone does not show that the work can finish.

Separate cloud steps from desktop steps

Microsoft describes Power Automate cloud flows as workflows connecting apps and services, with event, button and scheduled triggers. It also allows a cloud flow to trigger a desktop flow. For unattended desktop runs, Microsoft requires an available machine and documents Windows session conditions. A cloud trigger can therefore begin a process that still needs a particular computer. Ask whether the proposed job uses only online connections or opens software on a physical or virtual Windows machine. These distinctions describe Power Automate; check the equivalent requirements for your selected product.

Current primary documentation checked October 15, 2026. Supports cloud workflow and trigger descriptions; office-computer independence remains conditional on the complete dependency card and demonstration. Microsoft: cloud flows and their triggers

Supports triggering desktop work from a cloud flow and the machine/session dependency. The dependency card and computer-off exercise are original proposed checks, not a completed client integration. Microsoft: unattended desktop flows require an available machine

Write a short dependency card

For one task, record the trigger, source location, where processing runs, any computer it needs, destination, reviewer and evidence of completion. Consider a fictional office that wants an evening enquiry summary. A form stored online and an online review queue may support a route independent of the receptionist's laptop. If the same workflow reads a spreadsheet stored only on that laptop, or opens its job program to collect details, that step changes the requirement. Put every such dependency on the card rather than describing the whole process simply as cloud automation.

Request a harmless computer-off demonstration

In an agreed test environment, create a clearly labelled fictional enquiry and switch off the office computer that is claimed to be unnecessary. Let the proposed trigger run through its normal route. Check the test reference in the actual review queue, the source details and the completion time. A calendar entry, start notification or generated paragraph is insufficient evidence that the destination received it. Keep this exercise away from real customer messages and live financial changes. If a required step waits for a computer to return, record that limit and decide whether next-morning processing is acceptable.

Understand what a hosted machine changes

Microsoft offers hosted machines for desktop flows without requiring you to supply physical hardware. Its documentation identifies a Hosted Process licence and other prerequisites. Hosting can move a desktop dependency away from your office computer; it does not remove the application, access, session or maintenance requirements. Ask who provides and maintains that machine, how the required software is installed and what is included in the recurring cost. Do not assume that an ordinary AI subscription includes a hosted desktop or permission to run the chosen business software there.

Supports a hosted desktop option without supplied physical machines and separate licensing prerequisites. No price, universal compatibility or uptime guarantee is claimed. Microsoft: hosted machines and their prerequisites

Keep approval hours separate from collection hours

An online process might collect enquiries overnight while a staff member reviews them during working hours. Define these as separate outcomes. An unanswered request remains pending, even if the system collected it successfully. Agree who checks a failed or delayed item, where the work waits and how the team continues manually. Before rerunning a task, check whether the destination already received its result. The related recovery guide covers that operating handover; a machine being online is not a guarantee of successful processing.

Related Exovara guide: completion evidence, retry boundaries and manual recovery remain necessary beyond hosting. Agree what happens when an automation fails

Pay for the availability the task needs

Compare the current method with the proposed one using completed jobs, staff checking minutes and missed or delayed work. Include hosting, software, usage, monitoring and maintenance in the cost sheet. Value returned staff capacity separately from any measured additional sales. A morning summary may tolerate a morning run, while a genuinely time-sensitive intake task may justify independent hosting. Exovara can map the dependencies in your existing tools, test the required operating hours and scope the smallest useful setup. Agree the demonstrated result and support responsibility before relying on it after hours.

Related Exovara guide: approved exports, connectors and desktop interaction have different requirements. Check connections to your existing business software

Want help putting this to work?

This guide applies across Canada. We provide remote AI consulting for businesses in Burnaby; it does not describe a local client or a staffed office.

AI help in Burnaby · See how we can help · View pricing and scope