@uipath/skills 1.195.0

package/skills/uipath-troubleshoot/references/activity-packages/o365-activities/playbooks/mail-folder-not-found.md

@@ -0,0 +1,47 @@
+---
+confidence: high
+---
+
+# O365 — Mail folder not found
+
+## Context
+
+What this looks like — any of the following message patterns, all originating from the same root cause (the configured mail folder cannot be resolved against the user's mailbox):
+
+- `The resource could not be found.` 
+- `Folder named '<name>' could not be found on this account.` 
+- `Cannot find item configured with connection <connection> at path <folderName>.` — wrapper around the above. The original `Folder named ...` text is preserved as the inner exception's message.
+- `Value cannot be null. (Parameter 'Folder named '<name>' could not be found on this account.')` — same as above when the `ArgumentNullException` is surfaced unwrapped. Match on the inner sentence.
+
+The job faults synchronously the moment the activity tries to resolve the destination folder.
+
+What activities can produce this error:
+- **Move Email** (`MoveEmailConnections`) — `MailFolder` argument when the destination folder doesn't exist and `CreateFolderIfMissing = false`. Legacy: `MoveMail` (`DestinationFolderName`).
+- **Get Newest Email** (`GetNewestEmail`) — `MailFolder` argument when the source folder doesn't exist.
+- **Get Email List** (`GetEmailListConnections`) — `MailFolder` argument when the source folder doesn't exist.
+- **For Each Email** (`ForEachEmailConnections`) — `MailFolder` argument when the source folder doesn't exist.
+- **Wait For Email Received** (`WaitForEmailReceived`) — `MailFolder` argument when the source folder doesn't exist.
+- **New Email Received trigger** (`NewEmailReceived`) — `MailFolder` argument on the trigger or its debug/healing sample lookup.
+- Any other Mail activity that reads a folder.
+
+What can cause it:
+- **Folder does not exist in the mailbox.** The configured folder name/path doesn't match any folder under the resolved account, or the folder ID points to a folder that has been deleted, moved out of scope, or never existed in this mailbox. The activity enumerates folders for the resolved `Account` and the target name does not appear (case-insensitive) — or Graph returns 404 for the ID.
+- **Wrong mailbox in scope.** The folder exists, but in a different mailbox than the one the activity resolves to (`Account` / `Shared Mailbox`). Common when the connection was re-authenticated against a different account, or when a shared mailbox was passed but the folder lives only in the user's own mailbox (or vice versa).
+- **Stale folder ID.** A folder ID captured from a previous run no longer resolves. Outlook folder IDs are mailbox-scoped — moving the folder between mailboxes invalidates the ID.
+- **Path-segment mismatch.** Folder paths split on `/` and `\`. A folder name that itself contains one of those characters can fail to match. Leading/trailing whitespace or invisible characters in the configured name will also miss the case-insensitive comparison.
+- **Insufficient scope to enumerate.** The connection lacks `Mail.Read` / `Mail.ReadWrite` / `Mail.ReadWrite.Shared` for the target mailbox, so the folder-list enumeration is empty or filtered. Graph may return 404 instead of 403 for cross-mailbox shared/delegated access.
+
+> **Different cause, do not apply this playbook:**
+> - `MarkAsReadUnreadConnections`, `DeleteEmailConnections`, `ArchiveEmailConnections`, `DownloadEmailConnections`, and similar message-by-ID activities surface `The resource could not be found.` for a missing **message** (not folder). The fix path is different — verify the message ID and mailbox, not the folder configuration.
+
+## Resolution
+
+The error is unambiguous; no further investigation is needed. Stop the investigation and ask the user to verify the target folder:
+
+1. **Confirm the folder still exists** in the target mailbox — check Outlook / Outlook on the Web for the exact `DisplayName` and parent path. The lookup is case-insensitive but otherwise exact: trailing whitespace, mismatched separators, or a renamed folder all cause this error.
+2. **Confirm the configured `MailFolder` argument matches** what's in the mailbox. For path-based input, paths split on `/` and `\`, so the activity expects e.g. `Inbox/Subfolder`, not the literal folder name when the folder is nested. For ID-based input, the ID must come from the same mailbox the activity is now running against.
+3. **Confirm the resolved mailbox** (`Account` / shared-mailbox argument) is the one that owns the folder. If the connection has been re-authenticated against a different user, or if the activity is targeting a shared mailbox the connection cannot enumerate, the folder will not appear in the lookup.
+4. **For `MoveEmailConnections`**, ask the user whether the folder is expected to exist beforehand. If the folder should be created on the fly, set `CreateFolderIfMissing = true` to create any missing path segments instead of throwing.
+5. **Confirm the connection's scopes.** The connection must have `Mail.Read` (or `Mail.ReadWrite` for write operations), and `Mail.ReadWrite.Shared` for delegated/shared mailbox access. Missing scopes can surface as a 404 on enumeration even though the folder physically exists.
+
+If the user confirms the folder exists with the exact configured name in the resolved mailbox, the connection has the required scopes, and the identifier is correct, the cause is outside the activity — escalate (mailbox-level permissions, retention policy that hid the folder, or a Graph-side delay after a recent rename) rather than continue under this playbook.

package/skills/uipath-troubleshoot/references/activity-packages/o365-activities/presentation.md

@@ -0,0 +1,19 @@
+# Microsoft Office 365 Activities Presentation Rules
+
+- **Activities** — use the display name in prose (e.g., "Get Newest Email", "Move Email", "Download File", "Mark As Read/Unread", "Add Sheet"). Include the class name in parentheses on first mention so an agent can match a stack trace (e.g., "Move Email (`MoveEmailConnections`)"). Don't lead with the fully qualified class name.
+- **Connections** — use the connection name as configured in Integration Service (e.g., "officeactivities"), not internal IDs. When the underlying account matters for the diagnostic, also state the authenticated Microsoft 365 user principal name.
+- **Mailboxes** — distinguish the user's own mailbox from a shared mailbox or delegated mailbox
+- **Mail folders** — use the user-visible folder name and parent path (e.g., "folder 'Inbox'", "folder 'Inbox/Customers/VIP'"). Don't substitute the internal Graph folder ID. For well-known folders, use the canonical Outlook display name (`Inbox`, `Sent Items`, `Drafts`, `Deleted Items`, `Archive`, `Junk Email`).
+- **Email messages** — refer to a message by its `Subject` plus `ReceivedDateTime` (e.g., "the message 'Q1 invoice' received 2026-04-15 09:14"), not by message ID (only show them when the ID itself is what failed to resolve).
+- **OneDrive / SharePoint items (files / folders)** — refer to a Drive item by its name with parent context (e.g., "file 'invoice.pdf' under '/Reports/2026'", "folder 'Inbox' under the 'Documents' library"). Include the item ID, URL, or drive-relative path only when the diagnostic requires it — for example, when the playbook is the 404 case and the identifier itself is what failed to resolve.
+- **Drives (OneDrive vs. SharePoint document libraries)** — distinguish the user's personal OneDrive from a SharePoint document library. For SharePoint, refer to the drive by the site URL plus library display name (e.g., "library 'Documents' under site `<siteUrl>`"), not by drive ID.
+- **Shared links** — refer to a sharing URL by its target (e.g., "the shared link to 'invoice.pdf'"), not by the long encoded URL. When the link itself failed to resolve, show the URL verbatim and note whether sharing is anonymous, organization-scoped, or person-scoped.
+- **Excel workbooks** — refer to a workbook by its file name (e.g., "workbook 'Q1 Forecast.xlsx'"), not by the underlying drive item ID. Workbooks are OneDrive/SharePoint files, so they also follow the Drive item rule above.
+- **Excel sheets (tabs inside a workbook)** — refer to a sheet by its name (e.g., "sheet 'Data'"), not by `sheetId`. When reporting a conflict on `Add Sheet` or `Rename Sheet`, show both the configured name and the existing sheet's name verbatim.
+- **`ConflictBehavior` values** — refer to conflict-behavior values by the activity-facing enum display names. When recommending a value to the user, also state in plain language what it does (e.g., "set `ConflictResolution = Rename` so the new item is auto-renamed").
+- **`CreateFolderIfMissing` (Move Email)** — when recommending this option, name it explicitly and state what it does: "set `CreateFolderIfMissing = true` so the destination mail folder is created if it doesn't exist". This option only exists on `MoveEmailConnections` for path-based folder input — don't suggest it for ID-based input or for other activities.
+- **Local file paths** — show the full local path as configured on the activity (e.g., `C:\Reports\invoice.pdf`), not just the file name. OneDrive/SharePoint paths and local Windows paths look similar — clarify which one you mean. Forward slashes are typical for OneDrive/SharePoint paths; backslashes are typical for local Windows paths.
+- **Connection scopes (delegated permissions)** — refer to scopes by their Microsoft Graph names (e.g., `Mail.Read`, `Mail.ReadWrite`, `Mail.ReadWrite.Shared`, `Files.Read.All`, `Files.ReadWrite.All`, `Sites.Read.All`, `Sites.ReadWrite.All`). When a scope is missing, name the specific scope and the operation that needs it — Graph can return 404 instead of 403 for missing-scope cases, so don't conflate the symptoms.
+- **SharePoint lists / list items** — refer to a list by its display name with site context (e.g., "list 'Tickets' on site `<siteUrl>`"), not by GUID. Refer to list items by a user-visible field (e.g., title) plus the list name, not by item ID.
+- **Calendars and events** — refer to a calendar by its display name (e.g., "calendar 'Team Holidays'"), not by ID. Refer to an event by its `Subject` plus `Start` time, not by event ID. When the calendar lives in a group mailbox, name the group.
+- **Filter criteria (Get Newest Email, Wait For Email Received, NewEmailReceived trigger)** — when reporting a "no match" result, restate the configured filter in plain language (e.g., "messages received in the last 1 hour from `<emailAddress>` with subject containing `<subject>`"), and state the exact run timestamp. Filter-based mail activities are time-sensitive — only messages received at or before the run time are eligible.

package/skills/uipath-troubleshoot/references/activity-packages/o365-activities/summary.md

@@ -0,0 +1,11 @@
+# Microsoft Office 365 Activities Playbooks
+
+**Investigation guide:** [investigation_guide.md](./investigation_guide.md) — data correlation rules and testing prerequisites for Microsoft Office 365 Activities investigations
+
+| Issue | Confidence | Description | Playbook |
+|-------|:---:|-------------|----------|
+| Get Newest Email — No Email Matched the Filter Criteria | High | Mailbox contains zero messages matching the configured filter at the moment the activity runs (`Office365Exception: No email matching the filter criteria, received in the last 1 hour has been found...`). | [get-newest-email-no-match.md](./playbooks/get-newest-email-no-match.md) |
+| Item Name Already Exists | High | Destination already contains an item with the target name and `ConflictBehavior = Fail` (`Office365Exception: The specified item name already exists.`). Raised by Files (`CreateFolderConnections`, `CopyItemConnections`, `MoveItemConnections`, `RenameItemConnections`, `UploadFilesConnections`), Excel (`CreateWorkbookConnections`, `AddSheetConnections`, `RenameSheetConnections`), and legacy activities equivalents. Conflict is on the OneDrive/SharePoint/Excel side. | [item-name-already-exists.md](./playbooks/item-name-already-exists.md) |
+| Download — Multiple Items Name Conflict | High | Download activity (`DownloadEmailConnections`, `DownloadFileConnections`, `DownloadEmailAttachments`) throws `Office365Exception: Multiple items with the name <name> found in the specified folder.` because the **local** destination folder already contains a file with that name and `ConflictResolution = Fail`, or two attachments on the same email resolve to the same local filename. | [download-multiple-items-name-conflict.md](./playbooks/download-multiple-items-name-conflict.md) |
+| Mail — Folder Not Found | High | Mail activity (`MoveEmailConnections`, `GetNewestEmail`, `GetEmailListConnections`, `ForEachEmailConnections`, `WaitForEmailReceived`, `NewEmailReceived` trigger, legacy `MoveMail`) cannot resolve the configured `MailFolder`. Surfaces as `Office365Exception: The resource could not be found.`, `Folder named '<name>' could not be found on this account.`, or `Cannot find item configured with connection <connection> at path <folder>.`. | [mail-folder-not-found.md](./playbooks/mail-folder-not-found.md) |
+| Drive — File or Folder Not Found | High | OneDrive/SharePoint Drive activity (`GetFileFolderConnections`, `GetFileFolderMetadataConnections`, `GetFileListConnections`, `DownloadFileConnections`, `MoveItemConnections`, `CopyItemConnections`, `RenameItemConnections`, `DeleteItemConnections`, `ShareItemConnections`, `UpdateFileFolderMetadataConnections`, `CreateFolderConnections`, `UploadFilesConnections`, `ForEachFileFolderConnections`, `CheckinCheckoutFileConnections`, `AssignSensitivityLabelConnections`, `GetSensitivityLabelsConnections`, persistence `WaitForFile*`, legacy activities equivalents) cannot resolve the configured item. Surfaces as `Office365Exception: The resource could not be found.` or as the wrapping form `Cannot find item configured with connection <connection> at path <path>.` | [drive-item-not-found.md](./playbooks/drive-item-not-found.md) |

package/skills/uipath-troubleshoot/references/activity-packages/system-activities/investigation_guide.md

@@ -0,0 +1,25 @@
+# System Activities Investigation Guide
+
+## Data Correlation
+
+Before using any fetched data, verify it matches the user's reported problem:
+
+- **Activity** — the faulted activity name and namespace match the reported failure (e.g., `UiPath.Core.Activities.GetAsset` vs `UiPath.Core.Activities.GetCredential`)
+- **Asset/Credential name** — the name in the error or job trace matches the asset the user is asking about
+- **Folder** — the Orchestrator folder where the job ran is the same folder the user referenced
+- **Robot account** — the executing robot identity matches the one the user reported (check job details)
+- **Timestamp** — the failure occurred during the time window the user reported
+
+If the data doesn't match: **discard it**. Do NOT use unrelated data as a proxy. Report the mismatch and ask for clarification.
+
+## Testing Prerequisites
+
+When testing hypotheses for System Activities issues, gather and verify these before drawing conclusions:
+
+1. **Activity type** — identify the exact activity that faulted (Get Asset vs Get Credential vs Get Robot Asset vs Get Orchestrator Asset)
+2. **Asset name and type** — the exact asset name used in the activity, and whether it is Text, Integer, Boolean, or Credential in Orchestrator
+3. **Execution folder** — which Orchestrator folder the job ran in, and whether it is a classic or modern folder
+4. **Robot identity** — the robot account, its role, and whether it has View permission on Assets in the target folder
+5. **Robot connectivity** — whether the robot is Connected + Licensed in the Orchestrator Robots view
+6. **Package version** — confirm `UiPath.System.Activities` version; authentication and asset retrieval behavior differs across versions (especially 20.10.x, 2021.10.x, 22.10.x)
+7. **Credential store type** — if using an external vault (CyberArk, Azure Key Vault, Thycotic), confirm the vault type and check connectivity separately

package/skills/uipath-troubleshoot/references/activity-packages/system-activities/overview.md

@@ -0,0 +1,29 @@
+# System Activities
+
+Core workflow activities from the `UiPath.System.Activities` package that interact with Orchestrator resources at runtime. These activities are used inside workflows to read and write platform data — assets, credentials, queue items, storage buckets, and job metadata.
+
+## Key Activity Types
+
+- **Get Asset / Get Orchestrator Asset** — retrieve a text, integer, boolean, or JSON asset value from Orchestrator
+- **Get Credential / Get Orchestrator Credential** — retrieve a username/password pair from Orchestrator (returns `String` + `SecureString`)
+- **Get Robot Asset** — retrieve an asset value scoped to the executing robot (legacy; replaced by Get Orchestrator Asset in modern folders)
+- **Add Queue Item / Add Transaction Item** — push items into Orchestrator queues
+- **Get Transaction Item** — pull the next item from a queue for processing
+- **Set Asset** — update an asset value in Orchestrator
+- **Set Credential** — update a credential in Orchestrator
+
+## Common Failure Patterns
+
+- Asset or credential not found (name mismatch, wrong folder)
+- Permission denied (robot account lacks View/Edit on Assets)
+- Wrong activity for the asset type (Get Asset on a Credential, or vice versa)
+- Folder scope mismatch (modern vs classic folders, incorrect `OrchestratorFolderPath`)
+- External credential store unreachable (CyberArk, Azure Key Vault, Thycotic)
+- Robot not authenticated or not licensed
+- Network/TLS issues between robot and Orchestrator
+
+## Package
+
+NuGet: `UiPath.System.Activities`
+
+Version-specific bugs are documented in the relevant playbooks.

package/skills/uipath-troubleshoot/references/activity-packages/system-activities/playbooks/get-asset-activity-bug-silent-failure.md

@@ -0,0 +1,35 @@
+---
+confidence: medium
+---
+
+# Get Asset Failed — Activity Bug / Silent Failure
+
+## Context
+
+A `Get Asset` or `Get Orchestrator Asset` activity completes without throwing an exception, but the output variable is null, zero, or empty.
+
+What this looks like:
+- Activity completes successfully (no exception in job traces)
+- Output variable contains null, zero, or empty string instead of the expected asset value
+- Downstream logic fails because it receives an unexpected empty value
+
+What can cause it:
+- Activity was copy-pasted from another sequence — copy-paste retains internal state from the original activity
+- `UiPath.System.Activities` package version 22.10.x has a bug where variables created with `Ctrl+K` do not receive output values
+- Output variable was created via `Ctrl+K` during activity configuration in the affected version
+
+What to look for:
+- Whether the activity was copy-pasted from another sequence
+- The `UiPath.System.Activities` package version (especially 22.10.x)
+- How the output variable was created (pre-created in Variables panel vs `Ctrl+K`)
+
+## Investigation
+
+1. Check whether the activity was copy-pasted from another sequence — copy-paste retains internal state from the original.
+2. Check the Studio and `UiPath.System.Activities` package version — version 22.10.x has a bug where variables created with `Ctrl+K` do not receive output values.
+3. Verify the output variable was created before the activity (not via `Ctrl+K` during activity configuration in the affected version).
+
+## Resolution
+
+- **If copy-paste issue:** delete the activity and re-drag a fresh one from the Activities panel.
+- **If `Ctrl+K` variable bug (System.Activities 22.10.x):** update the package to ≥22.10.4, or pre-create the variable in the Variables panel before wiring it to the activity.

package/skills/uipath-troubleshoot/references/activity-packages/system-activities/playbooks/get-asset-external-vault-failure.md

@@ -0,0 +1,40 @@
+---
+confidence: medium
+---
+
+# Get Asset Failed — External Credential Store Failure
+
+## Context
+
+A `Get Credential` or `Get Orchestrator Credential` activity failed because the external credential store (CyberArk, Azure Key Vault, Thycotic, or other vault) is unreachable or misconfigured.
+
+What this looks like:
+- Error code 2303: `"Invalid Credential Store configuration"`
+- Error code 2304: `"Failed to read from Credential Store type <X>"`
+
+What can cause it:
+- Vault endpoint unreachable from the Orchestrator server (firewall, network)
+- CyberArk: FIPS mode enabled on Windows, 32/64-bit SDK mismatch, wrong web service name
+- Azure Key Vault: Orchestrator IP not whitelisted, secret contains backslash, wrong key-pair format
+- Thycotic: incorrect integration URL or credentials in Orchestrator settings
+- Credential store plugin settings incomplete or incorrect (error 2303)
+
+What to look for:
+- Vault type from the error message
+- Network connectivity between Orchestrator server and vault endpoint
+- Credential store configuration in Orchestrator > Credential Stores
+
+## Investigation
+
+1. Identify the vault type from the error message.
+2. Verify Orchestrator can reach the vault endpoint — check firewall/network rules from the Orchestrator server.
+3. For **CyberArk**: check for FIPS mode on Windows (incompatible with CyberArk SDK), 32/64-bit SDK mismatch, and web service name in Orchestrator credential store settings. On Orchestrator 2020.10.8–2021.10.1, set `Plugins.SecureStores.CyberArk.UsePowerShellCLI=false` in configuration (fixed in 2022.4+).
+4. For **Azure Key Vault**: verify the Orchestrator server IP is whitelisted in Key Vault network settings, the secret value does not contain a backslash (`\`), and the secret is in the expected key-pair format.
+5. For **Thycotic**: verify integration settings (URL, credentials) in Orchestrator > Credential Stores.
+6. For error 2303: check all credential store plugin settings (URL, application ID, credentials) for completeness and correctness.
+
+## Resolution
+
+- **If vault endpoint unreachable:** open network access from the Orchestrator server to the vault, then retest.
+- **If vault configuration incorrect:** fix the specific misconfiguration identified above and re-test by running the job.
+- **If secret format is wrong:** update the secret in the vault to match the expected format.

package/skills/uipath-troubleshoot/references/activity-packages/system-activities/playbooks/get-asset-folder-scope-mismatch.md

@@ -0,0 +1,38 @@
+---
+confidence: high
+---
+
+# Get Asset Failed — Folder Scope Mismatch
+
+## Context
+
+A `Get Asset`, `Get Orchestrator Asset`, or `Get Credential` activity failed because the activity targets the wrong folder or the folder type is incompatible.
+
+What this looks like:
+- Error code 1100: `"Folder does not exist or the user does not have access to the folder"`
+- Error code 1101: `"An organization unit is required"`
+
+What can cause it:
+- `OrchestratorFolderPath` property set to a wrong or nonexistent folder
+- Activity created before modern folders were introduced — lacks the FolderPath property entirely (error 1101)
+- Asset is in a classic folder but the job runs in a modern folder, or vice versa
+- Robot account is not assigned to the folder containing the asset
+
+What to look for:
+- The `OrchestratorFolderPath` property value on the activity
+- Whether the folder is classic or modern
+- Whether the robot account is assigned to the target folder
+
+## Investigation
+
+1. Check the `OrchestratorFolderPath` property of the activity — an incorrect or missing value is the most common cause.
+2. Confirm whether the asset is in a classic or modern folder, and whether the job runs in the same type.
+3. If error is 1101, the activity was likely created before modern folders were introduced — it lacks the FolderPath property entirely.
+4. Verify that the robot account is assigned to the folder containing the asset.
+
+## Resolution
+
+- **If `OrchestratorFolderPath` is wrong:** correct it or leave it blank to use the robot's connected folder.
+- **If error is 1101 (old XAML migration):** delete the activity and re-add it from the Activities panel in the current Studio version to generate the FolderPath property.
+- **If classic/modern folder mismatch:** recreate the asset in the correct folder type — cross-type access is not supported.
+- Assets are **not** auto-migrated during classic-to-modern folder migration; recreate them manually.

package/skills/uipath-troubleshoot/references/activity-packages/system-activities/playbooks/get-asset-network-connectivity.md

@@ -0,0 +1,46 @@
+---
+confidence: low
+---
+
+# Get Asset Failed — Network or Connectivity Issue
+
+## Context
+
+A `Get Asset`, `Get Orchestrator Asset`, or `Get Credential` activity failed due to network, TLS, or proxy issues between the robot and Orchestrator.
+
+What this looks like:
+- `"Orchestrator information is not available"`
+- Timeout errors or SSL handshake failures
+- Intermittent failures with no consistent error code
+- Failures appear after ~2 hours in long-running processes (session expiry)
+
+What can cause it:
+- UiPath Robot Windows service not running
+- Robot cannot reach the Orchestrator URL (firewall, DNS, proxy)
+- Proxy requires authentication (UiPath Robot supports only unauthenticated proxies)
+- SSL certificate expired or not trusted by the robot machine
+- TLS Extended Master Secret (EMS) incompatibility (manifests as ~1 in 256 intermittent failures)
+- Orchestrator auth session expired in long-running processes
+
+What to look for:
+- Whether the Robot service is running on the machine
+- Network connectivity from the robot machine to the Orchestrator URL
+- Proxy and SSL/TLS configuration
+- Whether failures are intermittent or consistent
+- Whether failures correlate with long-running process duration
+
+## Investigation
+
+1. Confirm the UiPath Robot Windows service is running on the machine.
+2. Verify the robot can reach the Orchestrator URL — test from the robot machine.
+3. Check for proxy configuration: UiPath Robot supports only unauthenticated proxies.
+4. For on-premises Orchestrator: verify the SSL certificate is valid and trusted by the robot machine's certificate store.
+5. If failures appear intermittent (~1 in 256 attempts): investigate TLS Extended Master Secret (EMS) compatibility.
+6. If failures occur after ~2 hours in long-running processes: the Orchestrator auth session has expired — implement retry logic around the Get Asset call.
+
+## Resolution
+
+- **If Robot service is stopped:** start it and re-run the job.
+- **If proxy is blocking:** configure the proxy to allow unauthenticated pass-through, or exclude the Orchestrator URL.
+- **If SSL certificate is expired:** renew it on the Orchestrator server and ensure the robot machine trusts it.
+- **If session expiry in long-running jobs:** add retry handling (Retry Scope) around the Get Asset activity.

package/skills/uipath-troubleshoot/references/activity-packages/system-activities/playbooks/get-asset-not-found.md

@@ -0,0 +1,35 @@
+---
+confidence: high
+---
+
+# Get Asset Failed — Asset Does Not Exist
+
+## Context
+
+A `Get Asset`, `Get Orchestrator Asset`, or `Get Credential` activity failed because the asset was not found in the Orchestrator folder where the job runs.
+
+What this looks like:
+- Error message contains `"Could not find an asset with this name"` or `"Could not find the asset"` (Error code: 1002)
+
+What can cause it:
+- Asset name in the workflow does not match any asset in the folder (typo, spacing, or rename)
+- Asset exists in a different folder than where the job runs
+- Asset was recently deleted or moved
+
+What to look for:
+- Exact asset name from the activity's AssetName property (in XAML or job traces)
+- The Orchestrator folder the job runs in (from job details)
+
+## Investigation
+
+1. Get the exact asset name from the activity's AssetName property (check XAML or job traces).
+2. Confirm the folder the job runs in (check the job details in Orchestrator > Jobs).
+3. List assets in that folder and verify an asset with that exact name exists.
+4. Check for case or spacing differences — asset names are not case-sensitive but spelling must match exactly.
+5. If the asset is missing, check whether it exists in a different folder or was recently renamed/deleted.
+
+## Resolution
+
+- **If the asset does not exist in the job folder:** create it there, or run the job in the folder where the asset is defined.
+- **If the name does not match:** fix the AssetName property in the workflow to match the Orchestrator asset name exactly.
+- **If the asset was deleted:** recreate it with the correct name, type, and value.

package/skills/uipath-troubleshoot/references/activity-packages/system-activities/playbooks/get-asset-per-robot-no-value.md

@@ -0,0 +1,31 @@
+---
+confidence: high
+---
+
+# Get Asset Failed — Per-Robot Asset Has No Value
+
+## Context
+
+A `Get Asset` or `Get Orchestrator Asset` activity failed because the asset is configured with per-robot values and the executing robot has no value assigned.
+
+What this looks like:
+- Error message contains `"The asset does not have a value associated with this robot"`
+
+What can cause it:
+- Asset uses "Per Robot" (or "Per Account/Machine") value mode but no entry exists for the executing robot
+- New robot was added to the folder without updating the asset's per-robot value table
+
+What to look for:
+- The asset name and its value mode (Global vs Per Robot) in Orchestrator
+- Whether the executing robot has a value entry in the asset
+
+## Investigation
+
+1. Navigate to Orchestrator > folder > Assets and open the asset.
+2. Confirm the asset is configured with "Per Robot" (or "Per Account/Machine") values.
+3. Check whether the robot executing the job has a value entry assigned.
+
+## Resolution
+
+- **If no value entry for the robot:** add a value entry for the executing robot in the asset's per-robot value table.
+- **If per-robot values are not required:** switch the asset to a global value.

package/skills/uipath-troubleshoot/references/activity-packages/system-activities/playbooks/get-asset-permission-denied.md

@@ -0,0 +1,33 @@
+---
+confidence: high
+---
+
+# Get Asset Failed — Permission Denied
+
+## Context
+
+A `Get Asset`, `Get Orchestrator Asset`, or `Get Credential` activity failed because the robot account lacks the required permissions on Assets in the Orchestrator folder.
+
+What this looks like:
+- Error message contains `"does not have the required permissions"`, `"You are not authorized!"`, or HTTP 403 `"Forbidden"` (Error code: 0)
+
+What can cause it:
+- Robot account role does not include View permission on Assets
+- Robot account is not assigned to the folder where the asset lives
+- Windows user running the process differs from the registered robot account
+
+What to look for:
+- The robot account running the job (from job details in Orchestrator)
+- The role assigned to that account in the target folder
+
+## Investigation
+
+1. Identify the robot account running the job (check job details in Orchestrator).
+2. In Orchestrator, navigate to the folder > Manage > Accounts & Groups and check the robot account's assigned role.
+3. Verify the role includes the **View** permission on Assets.
+4. If using folder inheritance, check parent folder permissions as well.
+
+## Resolution
+
+- **If role lacks View Assets:** grant the robot account a role that includes "View Assets" permission in the folder where the asset lives. Common roles with this permission: Automation User, Automation Developer, Administrator.
+- **If Windows user mismatch:** align the Windows user running the process with the registered robot account, or reassign the robot.

package/skills/uipath-troubleshoot/references/activity-packages/system-activities/playbooks/get-asset-robot-not-authenticated.md

@@ -0,0 +1,40 @@
+---
+confidence: medium
+---
+
+# Get Asset Failed — Robot Not Authenticated or Unlicensed
+
+## Context
+
+A `Get Asset`, `Get Orchestrator Asset`, or `Get Credential` activity failed because the robot is not authenticated or not licensed against Orchestrator.
+
+What this looks like:
+- Error message contains `"You are not authenticated! Error code: 0"`
+- Robot shows as `Connected, Unlicensed` in Orchestrator
+- Only Background Process template jobs fail while RE-Framework jobs succeed (package version conflict)
+
+What can cause it:
+- Robot is not licensed in Orchestrator
+- Machine key or client credentials do not match what is configured in Orchestrator
+- `UiPath.System.Activities` package upgrade introduced an authentication regression (versions 20.10.1+ and 2021.10.5)
+- Interactive sign-in not enabled for the tenant
+
+What to look for:
+- Robot connection status in the UiPath Assistant tray icon (Connected + Licensed vs Connected + Unlicensed)
+- `UiPath.System.Activities` package version in the project
+- Whether the issue started after a package upgrade
+
+## Investigation
+
+1. Check the UiPath Robot tray icon — verify it shows "Connected, Licensed".
+2. If unlicensed, check the license assignment in Orchestrator > Tenant > Licenses.
+3. Verify the robot's machine key or client credentials match what is configured in Orchestrator.
+4. Check whether the issue started after a `UiPath.System.Activities` package upgrade — versions 20.10.1+ and 2021.10.5 introduced authentication regressions.
+5. If only Background Process template jobs fail (not RE-Framework), the cause is likely a package version conflict.
+
+## Resolution
+
+- **If unlicensed:** assign a Runtime license to the robot in Orchestrator.
+- **If machine key mismatch:** reconnect the robot using the correct key from Orchestrator > Machines.
+- **If package regression:** downgrade `UiPath.System.Activities` to v20.4.x as a workaround, or update to the latest stable version.
+- **If interactive sign-in not enabled:** enable "Allow both user authentication and robot key authentication" in Tenant Settings > Security.

package/skills/uipath-troubleshoot/references/activity-packages/system-activities/playbooks/get-asset-wrong-activity-type.md

@@ -0,0 +1,32 @@
+---
+confidence: high
+---
+
+# Get Asset Failed — Wrong Activity for Asset Type
+
+## Context
+
+A `Get Asset` or `Get Credential` activity failed because the activity type does not match the asset type in Orchestrator.
+
+What this looks like:
+- Error message contains `"does not work with assets of type Credential"` or `"Invalid asset type"`
+- `Get Orchestrator Asset` used on a Credential asset, or `Get Credential` used on a Text/Integer/Boolean asset
+
+What can cause it:
+- Developer selected the wrong activity when building the workflow
+- Asset type was changed in Orchestrator after the workflow was built
+
+What to look for:
+- The asset name from the faulted activity
+- The asset type in Orchestrator (Text, Integer, Boolean, or Credential)
+
+## Investigation
+
+1. Identify the asset name from the faulted activity in the error message or job traces.
+2. Verify the asset type in Orchestrator — navigate to the folder > Assets and inspect the Type column.
+3. Confirm the workflow uses `Get Orchestrator Asset` when the asset is a Credential, or `Get Credential` when the asset is Text/Integer/Boolean.
+
+## Resolution
+
+- **If `Get Orchestrator Asset` on a Credential:** replace with `Get Orchestrator Credential`. Update downstream variable types — `Get Credential` returns a `SecureString` for the password and a `String` for the username.
+- **If `Get Credential` on a Text/Integer/Boolean asset:** replace with `Get Orchestrator Asset` (or `Get Asset`).

package/skills/uipath-troubleshoot/references/activity-packages/system-activities/presentation.md

@@ -0,0 +1,7 @@
+# System Activities Presentation Rules
+
+- **Activities** — use the display name (e.g., "Get Asset", "Get Credential"), not the fully qualified class name (e.g., `UiPath.Core.Activities.GetAsset`)
+- **Assets** — refer to assets by their Orchestrator name and type (e.g., "asset 'ApiBaseUrl' (Text)"), not by variable names used in the workflow
+- **Credentials** — refer to credentials by their Orchestrator name (e.g., "credential 'SAPLogin'"), not by the username or password variable names
+- **Folders** — use the full folder path as shown in Orchestrator (e.g., "Production/Finance"), not internal IDs
+- **Robots** — refer to robots by their display name or username, not by machine key or internal ID

package/skills/uipath-troubleshoot/references/activity-packages/system-activities/summary.md

@@ -0,0 +1,15 @@
+# System Activities Playbooks
+
+**Investigation guide:** [investigation_guide.md](./investigation_guide.md) — data correlation rules and testing prerequisites for System Activities investigations
+
+| Issue | Confidence | Description | Playbook |
+|-------|:---:|-------------|----------|
+| Get Asset — Wrong Activity for Asset Type | High | `Get Asset` used on a Credential or `Get Credential` used on a Text/Integer/Boolean asset | [get-asset-wrong-activity-type.md](./playbooks/get-asset-wrong-activity-type.md) |
+| Get Asset — Asset Does Not Exist | High | Asset not found in the Orchestrator folder where the job runs (error code 1002) | [get-asset-not-found.md](./playbooks/get-asset-not-found.md) |
+| Get Asset — Permission Denied | High | Robot account lacks View permission on Assets (HTTP 403, error code 0) | [get-asset-permission-denied.md](./playbooks/get-asset-permission-denied.md) |
+| Get Asset — Folder Scope Mismatch | High | Wrong `OrchestratorFolderPath` or classic/modern folder incompatibility (error codes 1100, 1101) | [get-asset-folder-scope-mismatch.md](./playbooks/get-asset-folder-scope-mismatch.md) |
+| Get Asset — Per-Robot Asset Has No Value | High | Per-robot asset has no value entry for the executing robot | [get-asset-per-robot-no-value.md](./playbooks/get-asset-per-robot-no-value.md) |
+| Get Asset — Robot Not Authenticated or Unlicensed | Medium | Robot not authenticated or not licensed against Orchestrator (error code 0, package regressions) | [get-asset-robot-not-authenticated.md](./playbooks/get-asset-robot-not-authenticated.md) |
+| Get Asset — External Credential Store Failure | Medium | External vault (CyberArk, Azure Key Vault, Thycotic) unreachable or misconfigured (error codes 2303, 2304) | [get-asset-external-vault-failure.md](./playbooks/get-asset-external-vault-failure.md) |
+| Get Asset — Activity Bug / Silent Failure | Medium | Activity completes without exception but output is null/zero/empty (copy-paste or package 22.10.x bug) | [get-asset-activity-bug-silent-failure.md](./playbooks/get-asset-activity-bug-silent-failure.md) |
+| Get Asset — Network or Connectivity Issue | Low | Network, TLS, proxy, or session expiry between robot and Orchestrator | [get-asset-network-connectivity.md](./playbooks/get-asset-network-connectivity.md) |