Sage schedules work with the Sage Edge Scheduler rather than a batch scheduler such as Slurm, so there are no queues, no partitions and no wall-clock limits. A job is an instance of a science goal, written in YAML or JSON: it names the edge applications to run, the nodes to run them on, the science rules that decide when they run, and the conditions that complete the job. Nodes are targeted individually by their VSN, for example W023, and a job can only target nodes your account is authorized to schedule on.
Two kinds of node run jobs, and neither is a queue. Wild Sage nodes are weatherproof outdoor nodes built around an NVIDIA Xavier NX ARM64 node controller with 8 GB of shared CPU and GPU memory and 1 TB of NVMe storage; they are the target for field deployments that process camera, audio, weather, air-quality, soil or water data where it is collected. Blade nodes are rack servers for machine rooms and other controlled sites, with a multi-core ARM64 processor, 32 GB of memory, a dedicated NVIDIA T4 GPU and 1 TB of SSD storage; they suit work that needs more GPU or memory than a Wild Sage node provides. See [Sage Architecture] for the full hardware description.
Jobs are created, submitted and removed with the sesctl client, which needs job-submission permission from [Request Sage Access] and an access token before it will talk to the scheduler. [Sage Submit your job] carries the configuration steps and the full command set.
Sage does not enforce job success criteria, so a submitted job is served until you remove it - a job file may carry a wall-clock criterion and it will not stop the job. Watch your jobs with sesctl stat and remove them when they are no longer needed.