Orchestration
3 min
min

Orchestration

Manage downloads across your network

The Solsta Orchestration Service queues and throttles installs across shared networks to prevent bottlenecks. All download operations flow through the queue automatically.

Add to Queue

Append --queue to any install, update, or repair command to schedule it for later execution.

Examples: 

Local Install

solsta_cli local install \  
--product_name=LlamaCraft \  
--env_name=dev-daily \  
--location=c:/builds/ --queue

Local Update

solsta_cli local update --all --queue
solsta_cli local repair \  
--product_name=LlamaCraft \  
--env_name=dev-nightly --queue

Check Queue Status

List all queued items for the current machine under the active credentials.

solsta_cli queue status
solsta_cli queue help

Run the Queue

Process all queued items on this machine. Items stay in the queue for 24 hours.

On a throttled network, the client waits up to 4 hours for its slot.

solsta_cli queue run
# Limit wait to 20 minutes on throttled networks
solsta_cli queue run \  
--orch_throttle_timeout=1200


solsta_cli queue run
# Limit wait to 20 minutes on throttled networks
solsta_cli queue run \  
--orch_throttle_timeout=1200

CLI and GUI Together

The Solsta CLI and Desktop Application are designed to coexist. However, the GUI does not reflect CLI changes in real time. Restart the GUI to see updates. If both run simultaneously, the GUI may occasionally pick up CLI operations from the orchestration service. Using --queue to schedule operations outside of GUI sessions is the safest approach.

A terminal error does not release the session slot. A retry on the same machine may be delayed by 10 minutes.