Schedule bots around app availability: Check application owners for maintenance and access windows.; Find overlap in available times for two or more apps.; Confirm machine is free, users signed out, and Power Automate plan is active.
Image: Business Automation Desk

RPA Operations

Part of RPA bot operations

Scheduling bots around application availability

Plan RPA runs around maintenance, runtime readiness, local time zones and business cut-offs, with a rule for missed windows.

Desk Automation Ops · · 2 min read

Schedule a bot for a window in which its target applications and runtime can support the work, with enough time to check the result before the business cut-off. A scheduled trigger is a request to start, not evidence that the bot started or finished on time.

Map the available window

Ask application owners about maintenance, batch processing, access restrictions and periods when records must not change. If a process uses two applications, find the overlap in their available windows. If it is too short, split the work with a reliable hand-off or choose another time.

Record the earliest permitted start, latest useful start, target finish and business cut-off. Leave time between the target finish and cut-off to inspect an exception and act on it. Also check whether another job or person may hold the same robot or records.

RPA Bot Execution Window: Key Time-Based Constraints

Earliest Permitted Start
As defined by application owners (e.g., after maintenance)
Latest Useful Start
Before system constraints prevent successful execution
Target Finish
Completion before business cut-off to allow verification
Business Cut-Off
Final deadline for data processing (e.g., end of day for payroll)

Set the calendar and runtime rules

Record the business time zone and compare it with the scheduler's configured zone. Review daylight-saving changes where relevant. Decide explicitly whether public holidays mean skipping, moving or separately approving the run.

Use the scheduler's documented options for time zones and non-working days. Verify actual starts and job outcomes rather than treating a scheduled trigger as proof of completion.

For Microsoft Power Automate unattended desktop flows, check machine and Windows session readiness as well. On Windows 10 and 11, any active user session, including a locked one, prevents an unattended run.

Confirm an available machine with all users signed out, the required Power Automate Process plan, and that the connection user can create a remote desktop session. In most cases, the user must be a member of the Remote Desktop Users group on the machine.

Handle a missed window

Set a late-start rule: run only if there is still time to finish and verify the result, hold the input for the next window, or hand it to an authorised manual owner.

Before relying on a schedule, review an ordinary day, maintenance overlap, holiday, busy robot and near-cut-off run using safe records. Compare requested start, actual start, finish and verified output. Review missed starts and late completions separately so the underlying constraint can be corrected.

Handling a Missed Execution Window

  1. Check if there is still time to finish and verify resultProceed with late start if possible
  2. Hold input for next available windowQueue for next scheduled run
  3. Hand off to authorised manual ownerEscalate if automation cannot complete in time

More from RPA Operations