You are writing a script that your colleagues could run on any Windows machine using...

The issue is the 40-KB limit associated with directly running raw script content. The safer method is to upload the script to the endpoint with put, then execute it from the host path using runscript -hostpath. This avoids forcing the full script body through a raw command execution path. Breaking the script into smaller files is operationally messy and increases the chance of partial execution or sequencing errors. runscript -cloudfile is used for scripts already available as cloud files or RTR-managed content, but the option that says to upload locally and execute directly misstates how that workflow functions. In RTR operations, the clean method for larger local scripts is to place the file on the endpoint and run it from the host path.