@uipath/skills 1.195.0 → 1.196.0

package/skills/uipath-platform/references/{resources → orchestrator}/process-queues.md

@@ -2,7 +2,7 @@
 
 Create work queues, add items for distributed processing, track progress, and manage review cycles.
 
-> For full option details on any command, use `--help` (e.g., `uip resource queues create --help`).
+> For full option details on any command, use `--help` (e.g., `uip or queues create --help`).
 
 ## When to Use
 
@@ -11,7 +11,7 @@ Create work queues, add items for distributed processing, track progress, and ma
 
 ## Prerequisites
 
-- Authenticated (`uip login`)
+- Authenticated — verify with `uip login status`; if not logged in, ask the user to run `uip login` (it opens an interactive browser flow)
 - Target folder exists (`uip or folders list`)
 
 ## Flow
@@ -21,7 +21,7 @@ graph LR
     A[queues create] --> B[queue-items add]
     B --> C[queue-items list]
     C --> D[queue-items get]
-    D --> E[set-progress]
+    D --> E[queue-items update]
     E --> F{Outcome}
     F -->|Failed| G[get-history]
     G --> H[set-reviewer]
@@ -36,7 +36,7 @@ graph LR
 ### Create a Queue
 
 ```bash
-uip resource queues create "InvoiceQueue" \
+uip or queues create "InvoiceQueue" \
   --folder-path "Finance" --max-retries 3 --auto-retry \
   --enforce-unique-reference --output json
 ```
@@ -57,7 +57,7 @@ Key options:
 ### List Queues
 
 ```bash
-uip resource queues list --folder-path "Finance" --output json
+uip or queues list --folder-path "Finance" --output json
 ```
 
 Filter by name with `--name` (contains match). Paginate with `--limit` / `--offset`.
@@ -66,36 +66,38 @@ Filter by name with `--name` (contains match). Paginate with `--limit` / `--offs
 
 ```bash
 # Get queue details (cross-folder, no --folder-path needed)
-uip resource queues get <queue-key> --output json
+uip or queues get <queue-key> --output json
 
 # Update queue properties (cross-folder)
-uip resource queues update <queue-key> --max-retries 5 --no-auto-retry --output json
+uip or queues update <queue-key> --max-retries 5 --no-auto-retry --output json
 
-# Delete queue (cross-folder)
-uip resource queues delete <queue-key> --output json
+# Delete queue (cross-folder). Refuses if the queue still has items;
+# pass --force to delete it and its items anyway.
+uip or queues delete <queue-key> --yes --output json
+uip or queues delete <queue-key> --force --output json
 ```
 
 ### Share a Queue Across Folders
 
 ```bash
 # Share with another folder
-uip resource queues share <queue-key> --folder-path "Production" --output json
+uip or queues share <queue-key> --folder-path "Production" --output json
 
 # Check which folders have access
-uip resource queues get-folders <queue-key> --output json
+uip or queues get-folders <queue-key> --output json
 
 # Remove from a folder
-uip resource queues unshare <queue-key> --folder-path "Production" --output json
+uip or queues unshare <queue-key> --folder-path "Production" --output json
 ```
 
 ### Queue Processing Stats
 
 ```bash
 # Stats for a specific queue (item counts, exception counts, processing times)
-uip resource queues get-stats --folder-path "Finance" --key <queue-key> --output json
+uip or queues get-stats --folder-path "Finance" --key <queue-key> --output json
 
 # Stats across queues in a folder, narrowed by name and a processing-window
-uip resource queues get-stats --folder-path "Finance" \
+uip or queues get-stats --folder-path "Finance" \
   --name "Invoice" \
   --from "2026-04-01T00:00:00Z" --to "2026-04-30T23:59:59Z" \
   --output json
@@ -110,7 +112,7 @@ uip resource queues get-stats --folder-path "Finance" \
 ### Add a Single Item
 
 ```bash
-uip resource queue-items add "InvoiceQueue" \
+uip or queue-items add "InvoiceQueue" \
   --folder-path "Finance" \
   --specific-content '{"InvoiceId":"INV-001","Amount":1500.00,"Vendor":"Acme"}' \
   --priority High --reference "INV-001" \
@@ -123,7 +125,7 @@ The `add` command takes a **queue name** (not key). Key options: `--specific-con
 ### Bulk Add Items
 
 ```bash
-uip resource queue-items bulk-add "InvoiceQueue" \
+uip or queue-items bulk-add "InvoiceQueue" \
   --folder-path "Finance" \
   --queue-items '[
     {"specificContent":{"InvoiceId":"INV-002","Amount":2000},"priority":"High"},
@@ -141,44 +143,51 @@ The `bulk-add` command also takes a **queue name**. Use `--commit-type` to contr
 | `StopOnFirstFailure` | Commits items until the first failure, then stops |
 | `ProcessAllIndependently` | Processes each item independently (default) |
 
+> The bulk-add API returns only a success flag and the list of failed items -- it does **not** return the created item keys. If you need the keys (e.g. to attach data or dispatch jobs), add items one at a time with `add` (which returns the created item), or `list --queue-name` afterward.
+
 ### List and Get Items
 
 ```bash
 # List items filtered by queue and status
-uip resource queue-items list --folder-path "Finance" \
+uip or queue-items list --folder-path "Finance" \
   --queue-name "InvoiceQueue" --status Failed --output json
 
+# List items across all accessible folders
+uip or queue-items list --all-folders --status Failed --output json
+
 # Get a single item by its unique key
-uip resource queue-items get <item-unique-key> --folder-path "Finance" --output json
+uip or queue-items get <item-unique-key> --folder-path "Finance" --output json
 ```
 
 Filter with `--queue-name` (exact match), `--queue-definition-key` (GUID), or `--status` (New, InProgress, Failed, Successful, Abandoned, Retried, Deleted).
 
-### Update, Set Progress, Delete
+### Update and Delete
 
 ```bash
 # Update item properties (only provided fields change)
-uip resource queue-items update <item-unique-key> --folder-path "Finance" \
-  --progress "Processing step 3/5" --priority High --output json
+uip or queue-items update <item-unique-key> --folder-path "Finance" \
+  --priority High --output json
 
-# Set progress text (positional argument)
-uip resource queue-items set-progress <item-unique-key> "Validating invoice data" \
-  --folder-path "Finance" --output json
+# Delete a single item by key
+uip or queue-items delete <item-unique-key> --folder-path "Finance" --yes --output json
 
-# Delete single / bulk
-uip resource queue-items delete <item-unique-key> --folder-path "Finance" --output json
-uip resource queue-items delete-bulk <key1> <key2> --folder-path "Finance" --output json
+# Delete several items in one call
+uip or queue-items delete-bulk <key1> <key2> --folder-path "Finance" --yes --output json
 ```
 
+`update` changes `--priority`, `--due-date`, `--defer-date`, and `--specific-content`. Progress is a work-in-progress message a running robot reports, so the CLI does not let you set it.
+
+`delete` (one key) and `delete-bulk` (a list of keys) are a **soft-delete**: the item's status changes to `Deleted`; it is not permanently removed.
+
 ### Get History and Retry Info
 
 ```bash
-uip resource queue-items get-history <item-unique-key> --folder-path "Finance" --output json
-uip resource queue-items get-last-retry <item-key> --folder-path "Finance" --output json
-uip resource queue-items has-video <item-unique-key> --folder-path "Finance" --output json
+uip or queue-items get-history <item-unique-key> --folder-path "Finance" --output json
+uip or queue-items get-last-retry <item-key> --folder-path "Finance" --output json
+uip or queue-items has-video <item-unique-key> --folder-path "Finance" --output json
 ```
 
-Note: `get-last-retry` uses the item `key` field (shared across retries), not `uniqueKey`.
+Note: `get-last-retry` uses the item `Key` field (shared across retries), not `UniqueKey`. Curated list/get output includes both.
 
 ---
 
@@ -190,28 +199,28 @@ When queue items fail, a reviewer can inspect them and decide whether to retry,
 
 ```bash
 # List available reviewers in the folder
-uip resource queue-items get-reviewers --folder-path "Finance" --output json
+uip or queue-items get-reviewers --folder-path "Finance" --output json
 
 # Assign a reviewer to one or more items
-uip resource queue-items set-reviewer <key1> <key2> \
+uip or queue-items set-reviewer <key1> <key2> \
   --folder-path "Finance" \
-  --user-id 42 \
+  --user-key <reviewer-key> \
   --output json
 ```
 
 ### Set Review Status
 
 ```bash
-uip resource queue-items set-review-status Retried <key1> <key2> \
+uip or queue-items set-review-status Retried <key1> <key2> \
   --folder-path "Finance" --output json
 ```
 
-Valid review statuses: `Retried`, `Abandoned`, `Deleted`. The status is the first positional argument, followed by one or more item keys.
+Valid review statuses: `None`, `InReview`, `Verified`, `Retried`. The status is the first positional argument, followed by one or more item keys.
 
 ### Remove Reviewer
 
 ```bash
-uip resource queue-items unset-reviewer <key1> <key2> \
+uip or queue-items unset-reviewer <key1> <key2> \
   --folder-path "Finance" --output json
 ```
 
@@ -221,27 +230,27 @@ uip resource queue-items unset-reviewer <key1> <key2> \
 
 ```bash
 # 1. Create the queue
-uip resource queues create "InvoiceQueue" \
+uip or queues create "InvoiceQueue" \
   --folder-path "Finance" --max-retries 3 --auto-retry \
   --enforce-unique-reference --output json
 
 # 2. Add work items (dispatcher)
-uip resource queue-items add "InvoiceQueue" --folder-path "Finance" \
+uip or queue-items add "InvoiceQueue" --folder-path "Finance" \
   --specific-content '{"InvoiceId":"INV-001","Amount":1500}' \
   --reference "INV-001" --priority High --output json
 
 # 3. Check for failed items (after performer runs)
-uip resource queue-items list --folder-path "Finance" \
+uip or queue-items list --folder-path "Finance" \
   --queue-name "InvoiceQueue" --status Failed --output json
 
 # 4. Investigate a failed item
-uip resource queue-items get-history <failed-item-key> \
+uip or queue-items get-history <failed-item-key> \
   --folder-path "Finance" --output json
 
 # 5. Assign reviewer and mark as reviewed
-uip resource queue-items set-reviewer <failed-item-key> \
-  --folder-path "Finance" --user-id 42 --output json
-uip resource queue-items set-review-status Retried <failed-item-key> \
+uip or queue-items set-reviewer <failed-item-key> \
+  --folder-path "Finance" --user-key <reviewer-key> --output json
+uip or queue-items set-review-status Retried <failed-item-key> \
   --folder-path "Finance" --output json
 ```
 
@@ -280,16 +289,18 @@ None --> InReview (reviewer assigned) --> Verified | Retried
 
 | Field | Scope | Use with |
 |-------|-------|----------|
-| `uniqueKey` | Unique per attempt | `get`, `update`, `delete`, `set-progress`, `get-history`, `has-video` |
-| `key` | Shared across retries | `get-last-retry` |
+| `UniqueKey` | Unique per attempt | `get`, `update`, `delete`, `get-history`, `has-video` |
+| `Key` | Shared across retries | `get-last-retry` |
 | Queue definition key | Queue identifier | `list --queue-definition-key`, `queues get` |
 
+Curated queue-item rows expose both `Key` and `UniqueKey` (PascalCase). With `--all-fields` you get the raw DTO instead, where the same fields are `key` / `uniqueKey`.
+
 ### Common Pitfalls
 
 - `--specific-content` must be **flat key-value JSON** -- no nested objects or arrays.
-- All `queue-items` commands require `--folder-path` or `--folder-key` (items are folder-scoped).
+- All `queue-items` commands require `--folder-path` or `--folder-key` (items are folder-scoped). Exception: `list` can take `--all-folders` instead to query across all accessible folders.
 - `set-review-status` takes the **status first**, then the item key(s) -- not the other way around.
-- `set-reviewer` requires `--user-id` (numeric ID, not GUID). Use `get-reviewers` to find valid IDs.
+- `set-reviewer` requires `--user-key` (GUID, not a numeric ID). Use `get-reviewers` to find reviewer keys.
 - Queue `get`, `update`, and `delete` are **cross-folder** (no `--folder-path` needed). Queue item commands are **not**.
 - `--auto-retry` is enabled by default. Use `--no-auto-retry` to disable.
 
@@ -297,6 +308,6 @@ None --> InReview (reviewer assigned) --> Verified | Retried
 
 ## Related
 
-- [resources.md](resources.md) -- Resource tool overview and libraries
+- [resources.md](resources.md) -- Orchestrator resources overview and libraries
 - [Triggers & Webhooks](triggers-and-webhooks.md) -- Queue triggers fire automations when item count exceeds a threshold
-- [Setup Environment](../orchestrator/setup-environment.md) -- Folder and machine setup
+- [Setup Environment](setup-environment.md) -- Folder and machine setup

package/skills/uipath-platform/references/{resources → orchestrator}/resources.md

@@ -1,10 +1,10 @@
-# Resources (`uip resource`)
+# Resources (`uip or`)
 
 Manage Orchestrator resources -- assets, queues, queue items, buckets, files, triggers, libraries, and webhooks.
 
-> **Important:** These commands use `uip resource`, NOT `uip or`. The old `storage-buckets`/`storage-bucket-files` names have been renamed to `buckets`/`bucket-files`.
+> **Important:** These commands live under `uip or` (the former standalone resource tool was retired and folded into `uip or`). The old `storage-buckets`/`storage-bucket-files` names are now `buckets`/`bucket-files`.
 
-> For full option details on any command, use `--help` (e.g., `uip resource assets list --help`).
+> For full option details on any command, use `--help` (e.g., `uip or assets list --help`).
 
 ---
 
@@ -25,7 +25,7 @@ Manage Orchestrator resources -- assets, queues, queue items, buckets, files, tr
 ## Command Tree
 
 ```
-uip resource
+uip or
   ├── assets              (9 verbs)
   ├── queues              (8 verbs)
   ├── queue-items         (15 verbs)
@@ -57,44 +57,44 @@ Libraries are tenant-scoped -- no folder context needed.
 
 | Command | Description |
 |---------|-------------|
-| `uip resource libraries list` | List libraries in the tenant feed. Options: `--limit <N>` (default 50), `--offset <N>`, `--sort-by "<field> <asc\|desc>"`. No native search — filter client-side via global `--output-filter "<JMESPath>"`. Returns `Key`, `Title`, `Version`, `Authors`. |
-| `uip resource libraries get <key>` | Get library details. Key format is `PackageId:Version` (e.g., `MyLib:1.0.0`). Returns the full API DTO. |
-| `uip resource libraries versions <package-id>` | List all versions of a library by package ID (the `Title` from `list` output). |
-| `uip resource libraries upload --file <path>` | Upload a `.nupkg` library package to the tenant feed. |
-| `uip resource libraries download <key> --destination <path>` | Download a `.nupkg` to local disk. |
-| `uip resource libraries delete <key>` | Delete a specific library version. |
+| `uip or libraries list` | List libraries in the tenant feed. Options: `--limit <N>` (default 50), `--offset <N>`, `--sort-by "<field> <asc\|desc>"`, `--all-fields`. No native search — filter client-side via global `--output-filter "<JMESPath>"`. Returns curated rows: `Key`, `Title`, `Version`, `Authors`, `Published`, `IsLatestVersion`, `IsPrerelease`, `ProjectType`. Note: `Published` is often empty on list rows (the bare collection endpoint doesn't populate it server-side); `get`/`versions` return it. |
+| `uip or libraries get <key>` | Get library details. Key format is `PackageId:Version` (e.g., `MyLib:1.0.0`). Returns a curated detail view (adds `Description`, `PackageSize`, `Created`, `LastUpdated`, etc.); `--all-fields` for the raw DTO. Dates the feed doesn't track are returned as empty strings (the API serializes 0001-01-01 sentinels; the CLI strips them). |
+| `uip or libraries versions <package-id>` | List all versions of a library by package ID (the `Title` from `list` output). Curated rows like `list`; `--all-fields` for raw. Fails with `Library not found` when the package ID doesn't exist (instead of an empty success). |
+| `uip or libraries upload --file <path>` | Upload a `.nupkg` library package to the tenant feed. The file must exist (checked client-side). The default shared feed is read-only on many tenants — if upload fails with a read-only/feed-not-found error, enable Tenant Libraries in tenant settings or target a writable feed with `--feed-id` (`uip or feeds list`). |
+| `uip or libraries download <key> --destination <path>` | Download a `.nupkg` to local disk. `--destination` creates missing parent dirs and overwrites an existing file. |
+| `uip or libraries delete <key>` | Delete a specific library version. Key format is `PackageId:Version` (validated client-side). |
 
 ```bash
 # List libraries (first 500). Default --limit is 50; bump it for tenants with many libraries.
-uip resource libraries list --limit 500 --output json
+uip or libraries list --limit 500 --output json
 
 # Filter by name client-side. Title can be null — guard with `Title != null` or contains() will error.
-uip resource libraries list --limit 500 \
+uip or libraries list --limit 500 \
   --output-filter "[?Title != null && contains(Title, 'Excel')]" \
   --output json
 
 # Multi-keyword OR filter
-uip resource libraries list --limit 500 \
+uip or libraries list --limit 500 \
   --output-filter "[?Title != null && (contains(Title, 'Common') || contains(Title, 'Shared'))]" \
   --output json
 
 # Upload a library
-uip resource libraries upload --file ./MyLibrary.1.0.0.nupkg --output json
+uip or libraries upload --file ./MyLibrary.1.0.0.nupkg --output json
 
 # List versions, then download a specific one
-uip resource libraries versions "UiPath.System.Activities" --output json
-uip resource libraries download "UiPath.System.Activities:24.10.0" \
+uip or libraries versions "UiPath.System.Activities" --output json
+uip or libraries download "UiPath.System.Activities:24.10.0" \
   --destination ./system-activities.nupkg --output json
 
 # Delete an old version
-uip resource libraries delete "UiPath.System.Activities:24.4.0" --output json
+uip or libraries delete "UiPath.System.Activities:24.4.0" --yes --output json
 ```
 
 ---
 
 ## Output Behavior
 
-Resource tool commands return **full API responses** (all fields) by default. There is no `--all-fields` flag — the convention in `resource-tool` is raw camelCase DTO. (This differs from `orchestrator-tool`, which curates by default and exposes `--all-fields` for the raw view; see [`uipath-orchestrator`](../orchestrator/orchestrator.md).)
+These commands return a **curated PascalCase view** by default — a focused projection of the most useful fields. Pass `--all-fields` on list/get-style commands to receive the raw API DTO instead (raw DTO keys are camelCase; the two shapes do not share casing). This matches the convention across all `uip or` commands; see [orchestrator.md](orchestrator.md).
 
 List responses include a `Pagination` block:
 
@@ -111,6 +111,6 @@ When `HasMore` is `true`, increment `--offset` by `--limit` and fetch again. Con
 
 ## Related
 
-- **Orchestrator** (`uip or`) — folders, jobs, processes, packages, users, machines → [`uipath-orchestrator`](../orchestrator/orchestrator.md)
-- **Solutions** (`uip solution`) — pack, publish, deploy solution packages → [`uipath-solution`](../solution/solution.md)
-- **Folder/user setup** — required before folder-scoped resources can be used → [`uipath-orchestrator/setup-environment`](../orchestrator/setup-environment.md)
+- **Orchestrator** (`uip or`) — folders, jobs, processes, packages, users, machines → [orchestrator.md](orchestrator.md)
+- **Solutions** (`uip solution`) — pack, publish, deploy solution packages → [`uipath-solution`](/uipath:uipath-solution)
+- **Folder/user setup** — required before folder-scoped resources can be used → [setup-environment.md](setup-environment.md)

package/skills/uipath-platform/references/orchestrator/run-jobs.md

@@ -13,7 +13,7 @@ Upload automation packages, bind them as processes, start jobs, and monitor exec
 
 ## Prerequisites
 
-- Authenticated (`uip login`)
+- Authenticated — verify with `uip login status`; if not logged in, ask the user to run `uip login` (it opens an interactive browser flow)
 - Target folder exists with machines assigned (see [setup-environment.md](setup-environment.md))
 - Automation package (.nupkg) built and ready to upload
 
@@ -44,6 +44,8 @@ uip or packages upload ./MyProcess.1.0.0.nupkg --feed-id <feed-key> --output jso
 
 Verify the upload and discover entry points before creating a process.
 
+> **Feeds:** `packages get`, `packages versions`, and `processes create` look in the **tenant** feed by default. If the package lives in a folder-hierarchy feed (a standard folder with its own feed), pass `--feed-id <feed-key>` — otherwise these return empty / 404 even though the package exists. (`processes create` itself no longer pre-checks the feed, so it succeeds in a folder feed regardless.)
+
 ```bash
 # Search for the uploaded package
 uip or packages list --search "MyProcess" --output json
@@ -86,7 +88,7 @@ Key options:
 |---|---|
 | `--entry-point <path>` | Required for multi-entry-point packages |
 | `--auto-update` / `--no-auto-update` | Auto-pick the latest package version on deploy |
-| `--job-priority <Low\|Normal\|High>` | Default execution priority |
+| `--job-priority <Low\|Normal\|High>` | Default execution priority. The CLI sets the matching `SpecificPriorityValue` band (Low=25, Normal=45, High=65) — the API derives the band from that value, so the change actually applies. |
 | `--specific-priority <1-100>` | Numeric priority override (mutually exclusive with `--job-priority`). Use when you need fine-grained ordering inside the same priority bucket. |
 | `--robot-size <Small\|Standard\|Medium\|Large>` | Cloud robot sizing for serverless runtimes |
 | `--input-arguments <json>` | Default input arguments (merged with per-job inputs) |
@@ -94,7 +96,7 @@ Key options:
 | `--tags <list>` | Comma-separated tags for filtering |
 | `--hidden-for-attended` / `--visible-for-attended` | Toggle visibility to attended robot users |
 | `--auto-create-triggers` / `--no-auto-create-triggers` | Auto-create connected triggers on deploy |
-| `--retention-period <days>` + `--retention-action <Delete\|Archive\|None>` (+ `--retention-bucket <id>`) | Job retention policy |
+| `--retention-period <days>` + `--retention-action <Delete\|Archive\|None>` (+ `--retention-bucket <id>`) | Job retention policy. `--retention-period` must be 1-180 (validated client-side). |
 | `--stale-retention-period <days>` + `--stale-retention-action <Delete\|Archive\|None>` | Stale-job retention policy |
 
 > The runtime kind (Unattended / Headless / NonProduction / AgentService / Serverless) is **not** a process-level setting; it's chosen per-job on `jobs start --runtime-type`. The process binds the package to a folder; runtime selection happens at execution time.
@@ -111,7 +113,7 @@ uip or processes resources <process-key-guid> --output json
 
 # Edit fields after creation. Same flag set as `processes create` minus name/package-key/package-version,
 # plus --healing-agent / --no-healing-agent (Autopilot for Robots toggle).
-uip or processes edit <process-key-guid> --description "Updated description" --output json
+uip or processes update <process-key-guid> --description "Updated description" --output json
 
 # Walk the package version history (every package version this release ever pointed at)
 uip or processes version-history <process-key-guid> --output json
@@ -123,10 +125,10 @@ uip or processes update-version <process-key-guid> --package-version 1.0.2 --out
 uip or processes rollback <process-key-guid> --output json
 
 # Delete the process (release). Package itself stays in the feed.
-uip or processes delete <process-key-guid> --output json
+uip or processes delete <process-key-guid> --yes --output json
 ```
 
-`processes edit` uses `Mapper.Map<ReleaseDto, UiRelease>(dto)` server-side, which means missing fields on the request body are nulled. The CLI works around this by spreading `currentRelease` as the baseline before applying overrides — but if you build the body yourself by hand, `tags`, `arguments`, `videoRecordingSettings`, `targetFramework`, `robotSize`, `resourceOverwrites`, `remoteControlAccess`, `targetRuntime`, `publisherLicense`, etc. will silently get nulled.
+`processes update` uses `Mapper.Map<ReleaseDto, UiRelease>(dto)` server-side, which means missing fields on the request body are nulled. The CLI works around this by spreading `currentRelease` as the baseline before applying overrides — but if you build the body yourself by hand, `tags`, `arguments`, `videoRecordingSettings`, `targetFramework`, `robotSize`, `resourceOverwrites`, `remoteControlAccess`, `targetRuntime`, `publisherLicense`, etc. will silently get nulled.
 
 ## Step 4: Start Job
 
@@ -144,12 +146,13 @@ uip or jobs start <process-key> --folder-path "Production" \
 
 Key options:
 
-- `--input-arguments <json>` / `--input-file <path>` — pick one. `--input-arguments` inlines a JSON object; `--input-file` uploads a file as the job's `InputFile` argument.
+- `--input-arguments <json>` / `--input-file <path>` — pick one. `--input-arguments` inlines a JSON object (validated client-side — invalid JSON is rejected before the call); `--input-file` uploads a file as the job's `InputFile` argument.
+  - **10K character cap on job arguments.** Orchestrator caps serialized input/output arguments at 10,240 characters for classic `StartJob` runs; an oversized output is silently dropped (the consuming workflow receives `null`, the job still reports Successful). `StartAgentJob` (agent runs) is not subject to the same cap in practice. Robot 2025.10.1+ removes the cap entirely ("Support for large input and output arguments"). If you hit it: pass big payloads via a storage bucket / queue item reference, or upgrade the Robot.
 - `--attachment <[name=]path>` — upload one or more files and attach them to the job. Repeat the flag for multiple. Pair with `--attachment-id <guid>` to reuse an attachment that was previously uploaded.
 - `--runtime-type <type>` — `Unattended`, `Headless`, `NonProduction`, `AgentService`, or `Serverless`. Picks the runtime kind the scheduler will use.
-- `--strategy <strategy>` — `ModernJobsCount` (default; spawn N independent jobs, paired with `--jobs-count`), `All` (run on every available robot in the folder), `Specific` (use `--user-keys` / `--machine-keys`).
+- `--strategy <strategy>` — one of `ModernJobsCount` (default; spawn N independent jobs, paired with `--jobs-count`), `All` (run on every available robot in the folder), `Specific` (use `--user-keys` / `--machine-keys`), or `JobsCount`. Validated client-side. `--jobs-count` must be a whole number greater than 0.
 - `--user-keys <guids>` / `--machine-keys <guids>` — comma-separated GUIDs to pin the job to specific identities. With `--strategy ModernJobsCount` they restrict the candidate pool; with `Specific` they're required.
-- `--healing-agent` — enable Autopilot for Robots (Healing Agent) just for this job, regardless of the process-level `--healing-agent` setting on `processes edit`. Useful for one-off self-healing without flipping the process default.
+- `--healing-agent` — enable Autopilot for Robots (Healing Agent) just for this job, regardless of the process-level `--healing-agent` setting on `processes update`. Useful for one-off self-healing without flipping the process default.
 - `--reference <text>` — user-set reference (free-form string) attached to the job. Useful for correlation with external systems.
 - `--environment-variables <json>` — JSON object of per-job environment variables. Merged on top of folder-/process-level env.
 - `--run-as-me` — run under the caller's identity instead of resolving an unattended robot account in the folder.
@@ -170,8 +173,13 @@ uip or jobs list --state Running --folder-path "Production" --output json
 
 # Filter by process name and date range
 uip or jobs list --process-name "MyProcess" --folder-path "Production" --output json
+
+# List jobs across all accessible folders
+uip or jobs list --all-folders --state Faulted --output json
 ```
 
+`jobs list` requires `--folder-path`, `--folder-key`, or `--all-folders` — a bare `jobs list` is rejected. (Older CLI versions listed tenant-wide by default; pass `--all-folders` for that behavior.)
+
 ## Step 6: Get Logs
 
 ```bash
@@ -190,7 +198,7 @@ Retrieve LLM and agentic execution traces for Agent-type processes:
 uip or jobs traces <job-key> --output json
 ```
 
-Traces are only available for processes that use UiPath Autopilot or Agent capabilities. For deeper span-level data, use `uip traces spans get [trace-id]` (or `uip traces spans get --job-key <key>`) — see [traces.md](../traces/traces.md).
+Traces are only available for processes that use UiPath Autopilot or Agent capabilities. For a standard Process the result is an empty list, and the response adds an `Instructions` note saying so — that's how you tell "no traces recorded" apart from "this isn't an Agent process". For deeper span-level data, use `uip traces spans get [trace-id]` (or `uip traces spans get --job-key <key>`) — see [traces.md](../traces/traces.md).
 
 Traces are cross-folder -- no `--folder-path` required.
 
@@ -217,19 +225,23 @@ uip or jobs history <job-key> --output json
 Control running or suspended jobs:
 
 ```bash
-# Stop a running job
+# Stop a running job (SoftStop is best-effort -- a job whose activity ignores
+# the cancellation token can still run to completion)
 uip or jobs stop <job-key> --strategy SoftStop --output json
 
 # Force-kill a job
 uip or jobs stop <job-key> --strategy Kill --output json
 
-# Restart a faulted or stopped job
+# Restart a finished job (any outcome -- faulted, stopped, or successful).
+# Returns the new run in the same { Jobs: [...] } shape as `jobs start`.
 uip or jobs restart <job-key> --output json
 
 # Resume a suspended job with new input
 uip or jobs resume <job-key> --input-arguments '{"approved": true}' --output json
 ```
 
+Jobs are immutable audit records -- there is no `jobs delete`. They age out per the binding process's retention period.
+
 ## Step 11: Manage Processes
 
 Update, rollback, or edit processes after deployment:
@@ -242,7 +254,7 @@ uip or processes update-version <process-key> --output json
 uip or processes rollback <process-key> --output json
 
 # Edit process properties
-uip or processes edit <process-key> --output json
+uip or processes update <process-key> --output json
 ```
 
 ---
@@ -329,4 +341,4 @@ uip or packages download "MyProcess:1.0.0" --destination ./packages/ --output js
 
 - [setup-environment.md](setup-environment.md) — Folder creation, machine assignment, user setup
 - [traces.md](../traces/traces.md) — Deep-dive into LLM/agentic traces and spans
-- Resources (assets, queues, buckets, triggers, webhooks, libraries) → [`uipath-resources`](../resources/resources.md)
+- Resources (assets, queues, buckets, triggers, webhooks, libraries) → [resources.md](resources.md)

package/skills/uipath-platform/references/orchestrator/setup-environment.md

@@ -13,7 +13,7 @@ Create folders, assign users with roles, provision machines, and configure licen
 
 ## Prerequisites
 
-1. Authenticated: `uip login`
+1. Authenticated — verify with `uip login status`; if not, ask the user to run `uip login` (interactive browser flow)
 2. Tenant selected: `uip login tenant set <tenant-name>`
 3. Sufficient permissions: tenant-level admin or folder-create rights.
 
@@ -24,7 +24,7 @@ Create folders, assign users with roles, provision machines, and configure licen
 ```mermaid
 graph LR
     A[folders create] --> B[roles create]
-    B --> C[roles edit<br/>add permissions]
+    B --> C[roles update<br/>add permissions]
     C --> D[users import]
     D --> E[users assign<br/>to folder + role]
     E --> F[machines create]
@@ -105,7 +105,7 @@ Roles group permissions and are scoped to either the tenant or a folder. Create
 uip or roles create --name "FinanceOperator" --type Folder --output json
 
 # Add permissions to the role
-uip or roles edit <role-key> \
+uip or roles update <role-key> \
   --add-permissions "Assets.View,Assets.Edit,Queues.View,Jobs.Create,Jobs.View" \
   --output json
 ```
@@ -199,7 +199,7 @@ uip or users get <user-key-guid> --output json
 uip or users list-available --folder-path "Finance" --search "jane" --output json
 
 # Edit principal-level flags (this is the only place to grant unattended on a DirectoryUser)
-uip or users edit <user-key-guid> \
+uip or users update <user-key-guid> \
   --allow-unattended \
   --license-type Unattended \
   --unattended-username "DOMAIN\\jane.doe" --unattended-password "<secret-or-cred-store-name>" \
@@ -209,16 +209,16 @@ uip or users edit <user-key-guid> \
 uip or users unassign <user-key-guid> --folder-path "Finance" --output json
 ```
 
-Key flags on `users edit`:
+Key flags on `users update`:
 
 - **License toggles** (mutually exclusive pairs): `--allow-unattended`/`--deny-unattended`, `--allow-attended`/`--deny-attended`, `--allow-login`/`--deny-login`, `--allow-personal-workspace`/`--deny-personal-workspace`, `--active`/`--inactive`.
 - `--license-type <Attended|Unattended|...>` — assigned license profile.
 - `--unattended-username <user>` and `--unattended-password <pass>` — Windows account + secret used for unattended execution. Required by the API as a pair when first toggling `--allow-unattended` on a `DirectoryUser`. Username typically `DOMAIN\\name` format. Password may be a literal secret or the name of an entry in a credential store (paired with `--credential-store-key <guid>`).
 - `--credential-store-key <guid>` — credential store backing `--unattended-password` when the secret is stored externally.
 
-`DirectoryRobot` principals don't need `--unattended-username` / `--unattended-password` on import — the robot identity already carries its own credentials in IS. Use `users edit --license-type Unattended` on the robot key to set the license profile.
+`DirectoryRobot` principals don't need `--unattended-username` / `--unattended-password` on import — the robot identity already carries its own credentials in IS. Use `users update --license-type Unattended` on the robot key to set the license profile.
 
-> **`users edit` does NOT expose role assignments.** It only touches tenant-side flags (license, session flags, unattended credentials). To change roles, use `uip or users assign` (folder roles), `uip or users assign-roles` (tenant roles), or `uip or roles users <role-key> --add-users/--remove-users` (single-role membership). Identity attributes like `--name`, `--surname`, `--email` on directory principals are sourced from Identity Service via sync — editing them via `users edit` only updates the Orchestrator-side cached copy and may be overwritten on the next IS sync.
+> **`users update` does NOT expose role assignments.** It only touches tenant-side flags (license, session flags, unattended credentials). To change roles, use `uip or users assign` (folder roles), `uip or users assign-roles` (tenant roles), or `uip or roles users <role-key> --add-users/--remove-users` (single-role membership). Identity attributes like `--name`, `--surname`, `--email` on directory principals are sourced from Identity Service via sync — updating them via `users update` only updates the Orchestrator-side cached copy and may be overwritten on the next IS sync.
 
 ### Step 5: Assign Users to Folders
 
@@ -276,7 +276,7 @@ Verify: `uip or machines list --folder-path "Finance" --output json`.
 uip or machines get <machine-key-guid> --output json
 
 # Edit slots, name, description (PATCH semantics — only provided fields change)
-uip or machines edit <machine-key-guid> \
+uip or machines update <machine-key-guid> \
   --unattended-slots 4 --headless-slots 2 \
   --name "finance-runner-01-renamed" --output json
 
@@ -284,17 +284,19 @@ uip or machines edit <machine-key-guid> \
 uip or machines unassign <machine-key-guid> --folder-path "Finance" --output json
 
 # Delete the machine template entirely (tenant-level)
-uip or machines delete <machine-key-guid> --output json
+uip or machines delete <machine-key-guid> --yes --output json
 
 # Bulk delete
-uip or machines delete <key1> <key2> --output json
+uip or machines delete <key1> <key2> --yes --output json
 ```
 
 Notes:
 
-- `machines edit` and `machines delete` resolve cross-folder by GUID — no `--folder-path` needed.
+- `machines update` and `machines delete` resolve cross-folder by GUID — no `--folder-path` needed. `machines update` echoes the new name when you rename.
+- Slot flags (`--unattended-slots`, `--headless-slots`, `--non-production-slots`, `--testing-slots`) must be whole numbers `>= 0` (validated client-side; `0` is allowed).
+- `machines delete` removes the machine **and** any folder assignments it has (the assignments are re-creatable config, so there is no `--force` gate). It does not require unassigning first.
 - Each folder accepts **one** Cloud Robots / Serverless machine. Trying to assign a second serverless to the same folder returns `HTTP 409: Only one Cloud Robots - Serverless is allowed per folder.`
-- `machines list` defaults to all machines visible to the user. With `--folder-path` it lists only machines assigned to that folder. Use `--all-fields` for the raw DTO including slot subtypes (`automationCloudSlots`, `automationCloudTestAutomationSlots`, etc.).
+- `machines list` defaults to all machines visible to the user. With `--folder-path`/`--folder-key` it returns only machines assigned to that folder, each with `IsAssignedToFolder`. Use `--all-fields` for the raw DTO including slot subtypes (`automationCloudSlots`, `automationCloudTestAutomationSlots`, etc.) — note `--all-fields` emits the raw camelCase DTO.
 
 ### Step 8: Configure Licenses
 
@@ -332,7 +334,7 @@ uip or folders create "Finance" -d "Finance department automations" --output jso
 uip or roles create --name "FinanceOperator" --type Folder --output json
 # Response: { "Data": { "Key": "r1r2r3r4-..." } }
 
-uip or roles edit r1r2r3r4-... \
+uip or roles update r1r2r3r4-... \
   --add-permissions "Assets.View,Assets.Edit,Queues.View,Jobs.Create,Jobs.View,Processes.View" \
   --output json
 
@@ -368,9 +370,9 @@ uip or machines list --folder-path "Finance" --output json
 
 ## Variations and Gotchas
 
-### Folder edit uses `edit`, not `update`
+### The mutation verb is `update` (`edit` is a deprecated alias)
 
-The verb is `edit` for both folders and machines: `uip or folders edit <key>`, not `update`.
+All five admin nouns use `update`: `uip or folders update <key>`, `machines update`, `processes update`, `roles update`, `users update`. The old `edit` spelling still works as a hidden alias for backward compatibility, but new scripts should use `update`.
 
 ### Users can be assigned without roles
 
@@ -398,6 +400,8 @@ The role-resolver utility fetches all roles to map GUIDs to numeric IDs. For ten
 
 Filtering options (`--type`, `--name`, `--path`, `--top-level`, `--sort-by`) only work with `--all`. Without `--all`, the command returns only folders the current user is assigned to and rejects filter flags.
 
+`folders list --all` rows also include `FeedType` (e.g. `FolderHierarchy`, `Processes`); the plain `folders list` does not (the current-user folders API doesn't return it). Use `--all` or `folders get` when you need `FeedType`.
+
 ### Personal workspaces are flat
 
 `uip or folders list --all --type personal` returns personal workspaces with a different shape (`Key`, `Name`, `OwnerName`, `OwnerKey`, `LastLogin`). The `--path` and `--top-level` flags are not supported because personal workspaces have no hierarchy.
@@ -407,4 +411,4 @@ Filtering options (`--type`, `--name`, `--path`, `--top-level`, `--sort-by`) onl
 ## Related
 
 - [Run Jobs](run-jobs.md) — After setup, deploy packages and start jobs in the folder.
-- Create assets, queues, and buckets in the folder → [`uipath-resources`](../resources/resources.md)
+- Create assets, queues, and buckets in the folder → [resources.md](resources.md)