CloudPilotRecord operations and replay in batches
Demonstrate a sequence on one master desktop, then replay it on several others in the same order and timing. Replay targets are selected separately from live-sync followers.
Updated October 15, 2026
Repeat creation, replay and deletion
In the Windows creation dialog, enable Replay after creation, then Repeat creation and replay. The workflow uses this form’s regions, counts, instance size, browser, URLs and your account’s saved recording. Set the replay delay, how many minutes to wait AFTER replay ends before deletion, and the number of rounds. The default is 3 rounds; 0 repeats until stopped. Each round creates instances, waits and replays in the background, waits after replay ends, and deletes that round’s instances. The next round starts only after deletion is confirmed. Only instances tagged and created by this workflow are deleted, including their data; other instances are unaffected. Standard EC2, Wavelength and Lightsail are supported, and execution continues after closing the page. In Scheduled tasks → Instance workflows, view stages, times, instances and recent rounds. Pause after this round finishes replay, the wait and cleanup before pausing. Stop and clean up stops further launches and playback, then cleans up this round; in-flight creation must settle first. Resume a paused workflow to continue. Each credential profile can have one running or paused workflow. Launch or replay failures are recorded without automatically pausing the loop. Created instances still proceed to replay and cleanup; the next round starts after deletion is confirmed. Temporary query or cleanup failures retry automatically and block new launches until cleanup is confirmed. A round that runs longer than the replay delay plus the deletion delay plus 24 hours (72 hours at most) is ended and cleaned up, then the schedule continues. Manual pause, stop and the configured round limit still apply. Expired account access or a changed AWS account blocks further launches. The recording and administrator password are encrypted for execution; changing the account recording does not affect an existing workflow. Execution configuration is removed on completion or stop. AWS and background replay usage continues each round. Keep credentials valid with permission to delete. Uploaded ZIP links still expire after 30 days; looping does not extend them. Shared networks, roles and manually added resources are outside automatic cleanup.
Schedule replay when creating instances
When creating built-in Windows instances, enable Replay after creation and choose a delay of 1–1440 minutes after the batch finishes. It uses the recording saved to your CloudPilot account; import one in Sync control and wait for the account save to finish first. The version is checked before creation, and each task stores an encrypted snapshot unaffected by later imports or deletion. Only successfully created instances are included; Standard EC2, Wavelength and Lightsail are supported. After successful submission, you may close the page. The server hands the task to background replay within about one minute of its due time, or queues it behind an active task on the same profile. Queued tasks expire after 24 hours. Newly created instances that are not yet running or visible get up to 30 minutes of startup retries. Webpage readiness is not detected, so allow time for installation and loading. Playback runs once; avoid controlling targets during replay. In Scheduled tasks, view records for the current credential profile, cancel pending tasks or open Background task to inspect or stop submitted replays in Sync control. Submission records are retained for 7 days; the queue removes its recording copy after handing it to the replay service.
Connect and prepare matching starting pages
Select multiple Windows instances in the dashboard, open Sync control and choose Connect only. Make the demonstration desktop the master. Prepare matching windows, page positions and browser zoom on the other targets, and wait until their connections are ready.
Start and stop recording on the master
Expand Record and replay operations, choose Start recording, perform clicks, scrolling, typing or pastes on the master, then choose Stop recording. Live sync pauses while recording; only the master is operated. Leave enough loading time between actions so playback does not advance too early.
Select targets and start batch replay
Use Select replay targets to choose individual desktops or all other desktops. The source of a recording made in this page is excluded. Imported recordings are not tied to the original instance and can also target the current master. Replay in this page is selected by default. Connect the targets at 1600 × 900, align their starting pages, select them and choose Replay here. Keep the page open and your network connected. Background replay (no connection needed) remains available by selecting it manually. These choices are separate from Follow selections.
Check progress or stop playback
With the default Replay in this page mode, keep the page open. A disconnected target pauses and resumes remaining input after reconnection at the matching resolution; each target has its own progress and stop control. Only after manually choosing Background replay and submitting successfully can execution continue after your computer disconnects, the page closes or your computer shuts down. Check per-target progress, stop one or all targets, or return to Sync control with the same credential profile to view the latest task for 7 days. Background replay connects up to 32 desktops within a single hosted browser page, with up to 32 targets running per credential profile and remaining targets queued. Each target retains independent progress, clipboard and stop controls; an RDP disconnect does not stop other desktops in the group. After the last input, the connection stays open for 1 minute to allow page loading and processing before disconnecting. You can stop during this buffer. An RDP disconnect reconnects with progress preserved. If the hosted browser itself exits, playback is interrupted to avoid repeating uncertain input. Delivery at the instant of disconnection cannot be confirmed; check any result notice. Explicit stop cancels continuation. Keep instances running and avoid operating target desktops.
Reuse, replace and retain a recording
Reuse the recording on other targets. Each replay starts the whole sequence from the beginning, so reset target pages first. Record again replaces the recording in this page. Download new recordings as JSON and import them if you want them restored next time. The last imported recording is saved encrypted to your CloudPilot account. Wait for Saved to account before leaving; it restores after refreshing, signing in again, or changing browsers and devices. Each account retains one imported recording, replaced when you import another file. Clear recording removes both the current recording and the account copy. Downloaded JSON files remain available for reuse.
Import and replay on new instances
Select instances in the dashboard and enter Sync control. Expand Record and replay operations, your saved account recording and filename restore automatically. To import for the first time or replace it, choose Import recording and select a saved JSON file. Once validated, it is saved encrypted to your account. Restoring or importing never selects targets or runs operations automatically, and the original instance does not need to exist. Connect the new instances, match starting pages, windows and zoom, then select targets and use the default Replay in this page mode. Background replay must be selected manually. Background tasks use a separate execution copy, removed when the task ends. The remembered account recording remains until you import a replacement or choose Clear recording. If saving fails, the recording remains usable in this page; retry or download a backup. Changes from another page trigger a conflict notice instead of silently overwriting the newer account copy. Import replaces the current recording; incompatible format, dimensions or contents produce an error and leave it unchanged.
Handle interruptions and recording limits
If the master disconnects, recording time pauses with earlier input retained and automatically resumes after reconnection. You can also stop recording while waiting. Limits are 30 minutes, 50,000 inputs and 8 MiB. Exceeding a limit discards the incomplete recording; record shorter sequences instead.
Recording files include actual typed and clipboard text and may contain passwords you entered. Store them carefully and only import files you trust. Playback uses coordinates without identifying buttons or waiting for page loads. Replay complete means input was sent; check each target page for the actual result.