@uipath/skills 1.195.0

package/skills/uipath-troubleshoot/references/activity-packages/gsuite-activities/playbooks/drive-file-not-found.md

@@ -0,0 +1,37 @@
+---
+confidence: high
+---
+
+# GSuite Drive — File or folder not found (HTTP 404)
+
+## Context
+
+What this looks like — any of the following messages, all originating from a Google API `HTTP 404 NotFound` response:
+
+- `File not found: <id>. [404]`
+- `The service drive has thrown an exception. HttpStatusCode is NotFound. File not found`
+- `The service sheets has thrown an exception. HttpStatusCode is NotFound. Requested entity was not found.`
+- `The resource was not found.`
+
+The job faults synchronously the moment the activity tries to resolve the resource.
+
+What activities can produce this error:
+Most `UiPath.GSuite.Activities` activities that take a Drive file, folder, spreadsheet, or document identifier (ID, URL, path, or browse selection) — for example: `GetFileFolderConnections`, `GetFileFolderInfoConnections`, `DownloadFileConnections`, `MoveFileConnections`, `CopyFileConnections`, `DeleteFileOrFolderConnections`, `RenameFileFolderConnections`, `ShareFileFolderConnections`, `UploadFilesConnections` (when targeting an existing parent folder), and any Sheets/Docs activity that opens a spreadsheet or document by ID.
+
+What can cause it:
+- The configured ID, URL, or path resolves to a Drive resource that no longer exists, has been moved to Trash, has been permanently deleted, or was never accessible to the authenticated account. This is the only cause the error can describe — Google has authoritatively returned `404 NotFound` for the request.
+
+> **Different cause, similar message — do not apply this playbook:**
+> - **`ApplyFileLabelsConnections`** can throw `The resource was not found. Please make sure that the selected label is enabled for "Drive and Docs".` That is a label-configuration issue, not a missing file.
+> - **`The document with the name <name> was not found in the specified folder.`** is a name-based lookup miss (no document with that title in the parent), not a 404 against an ID. Treat as a separate scenario.
+> - **`File does not exist.`** (`FileNotFoundException`) refers to a missing **local filesystem** path (e.g., an upload source path or service-account key file), not a Drive resource.
+
+## Resolution
+
+The error is unambiguous; no further investigation is needed. Stop the investigation and ask the user to verify the target resource:
+
+1. **Confirm the file or folder still exists** in Google Drive (it may have been deleted, trashed, or moved out of the visible scope).
+2. **Confirm the configured identifier is correct** — the ID, URL, or path on the activity must point to the intended resource. Common mistakes: a stale ID copied from an older version of the file, a URL pointing to a different account's resource, a path that no longer matches the actual folder structure.
+3. **Confirm the connection's authenticated account has access** to the resource. A file owned by another user that was never shared with this account will also surface as `404 NotFound`.
+
+If the user confirms the resource exists, is reachable in the Drive UI under the same account, and the identifier is correct, the cause is outside the activity — escalate (connection scope, domain policy, sharing) rather than continue under this playbook.

package/skills/uipath-troubleshoot/references/activity-packages/gsuite-activities/playbooks/drive-multiple-items-name-conflict.md

@@ -0,0 +1,40 @@
+---
+confidence: high
+---
+
+# GSuite Drive — Multiple items with the same name in the specified folder
+
+## Context
+
+What this looks like:
+- An activity from `UiPath.GSuite.Activities` (Drive operations) throws `GSuiteException`
+- Error message: `Multiple items with the name <name> found in the specified folder.`
+- Job faults synchronously the moment the activity runs
+
+What activities can produce this error:
+- **Create Folder** (`CreateFolderConnections`) — `ConflictResolution = Fail` and a folder with that name already exists in the parent; or `ConflictResolution = UseExisting` and more than one folder with that name exists
+- **Copy File** (`CopyFileConnections`) — destination already contains an item with the target name (`Fail`) or contains more than one (`Replace`)
+- **Move File** (`MoveFileConnections`) — destination already contains an item with the target name (`Fail`) or more than one (`Replace`)
+- **Rename File or Folder** (`RenameFileFolderConnections`) — `ConflictResolution = Fail` and an item with the new name already exists in the same parent
+- **Upload Files** (`UploadFilesConnections`) — destination already contains an item with the target name (`Fail`) or more than one (`Replace`)
+- **Create Spreadsheet** (`CreateSpreadsheetConnections`) — a spreadsheet with that name already exists in the parent
+- **Create Document** (`CreateDocumentConnections`) — a document with that name already exists in the parent
+
+What can cause it:
+- The target Google Drive folder already contains one or more items with the same name as the new/target item, and the configured `ConflictResolution` ("conflict behavior") cannot resolve the conflict on its own. This is the only cause — the activity issues a name lookup against the Drive API in the parent folder and refuses to proceed.
+
+> **Different cause, same message:** `DownloadAttachmentsConnections` (Gmail) throws the same message when two attachments on the same email resolve to the same **local** destination path. That is unrelated to Drive `ConflictResolution`. If the faulted activity is `DownloadAttachmentsConnections`, do not apply this playbook.
+
+## Resolution
+
+The error is unambiguous; no further investigation is needed. Stop the investigation and ask the user to do one of the following:
+
+1. **Change the name** of the new/target item so it is unique within the destination folder.
+2. **Ensure the destination folder contains no item with that name** (rename, delete, or move the existing item).
+3. **Change the `ConflictResolution` (conflict behavior)** on the activity to a value that handles the duplicate:
+   - `Rename` — automatically rename the new item to a unique name
+   - `Replace` — replace the existing item (only when exactly one match exists; throws again if multiple matches)
+   - `AddSeparate` — always create a new copy alongside the existing item(s)
+   - `UseExisting` (Create Folder only) — return the existing folder instead of creating a new one (only when exactly one match exists)
+
+   `RenameFileFolderConnections` only supports `Fail` and `AddSeparate`. The other Drive activities support the full enum.

package/skills/uipath-troubleshoot/references/activity-packages/gsuite-activities/playbooks/get-newest-email-not-found.md

@@ -0,0 +1,32 @@
+---
+confidence: high
+---
+
+# GSuite Get Newest Email — no email matched the filter
+
+## Context
+
+What this looks like:
+- Activity `Get Newest Email` (UiPath.GSuite.Activities, GetNewestEmailConnections) throws `GmailException`
+- Error message: `No email matching the search criteria has been found`
+- Job faults synchronously the moment the activity runs — no retry, no wait
+
+What can cause it:
+- The Gmail mailbox contains zero messages matching the configured filter at the moment the activity executes. This is the only cause — the activity issues a single Gmail API query with `MaxResults = 1` and throws when the result is empty.
+
+What to look for:
+- The exact filter the activity was configured with: `Folder`, `FilterSelectionMode` (ConditionBuilder vs Query), `QueryFilter` (raw Gmail query), or the structured `Filter` collection (`From`, `To`, `Subject`, `Body`, `DateAndTime`, `Cc`, `Bcc`, `Categories`, `Filename`, `Labels`)
+- Boolean modifiers tightening the search: `UnreadOnly`, `WithAttachmentsOnly`, `ImportantOnly`, `StarredOnly`
+- The job run timestamp — only emails received at or before this moment are eligible
+
+## Investigation
+
+1. From the job logs or workflow, capture the exact values of every filter property listed above and the job start timestamp.
+2. Confirm the activity is `GetNewestEmailConnections` (display name "Get Newest Email") and not a long-running trigger — this activity does not poll or wait.
+3. There is nothing further to verify programmatically; the Gmail API has already authoritatively returned zero matches for that query. Proceed to Resolution.
+
+## Resolution
+
+- **In all cases:** Report the captured filter values and job timestamp to the user and ask them to sign in to the target Gmail mailbox and confirm whether any message matching those filters was present at or before the job run time. Then:
+  - **If no matching email existed:** This is expected behavior, not a defect. Recommend either (a) loosening the filter (remove `UnreadOnly`/`WithAttachmentsOnly`/`ImportantOnly`/`StarredOnly`, broaden `Subject`/`From`/`DateAndTime`, switch `FilterSelectionMode` to a less restrictive `QueryFilter`), or (b) wrapping the activity in a Try/Catch so the workflow handles the empty-mailbox case explicitly, or (c) scheduling the job to run after the expected email arrives.
+  - **If a matching email did exist in the mailbox at that time:** Ask the user to copy the matching message's raw Gmail search query (e.g., `from:foo@bar.com subject:"X" has:attachment`) and compare it against the activity's configured filter to identify the mismatch (common culprits: label scoping, `Folder` set to a label that excludes Inbox, time-zone offset on `DateAndTime`, case-sensitivity expectations that Gmail does not honor).

package/skills/uipath-troubleshoot/references/activity-packages/gsuite-activities/playbooks/sheets-cell-limit-exceeded.md

@@ -0,0 +1,46 @@
+---
+confidence: high
+---
+
+# GSuite Sheets — 10 million cell limit exceeded
+
+## Context
+
+What this looks like — `GSuiteException` carrying a Google Sheets API 400 BadRequest:
+
+`The service sheets has thrown an exception. HttpStatusCode is BadRequest. This action would increase the number of cells in the workbook above the limit of 10000000 cells.`
+
+The job faults synchronously the moment the activity issues the write or expand request. The Google message portion is fixed by Google and is not produced by the activity package.
+
+What activities can produce this error — any Sheets activity that writes cells or expands the grid:
+
+**Modern Connections activities**:
+- `WriteRangeConnections` — most common trigger; writing a DataTable to a range that extends past the current grid auto-expands the sheet
+- `WriteCellConnections` — writing a single cell past the existing grid auto-expands rows/columns
+- `WriteRowConnections` / `WriteColumnConnections` — writes that extend the grid past current bounds
+- `AutoFillRangeConnections` — extends a pattern from a seed range; can expand the grid
+- `CopyPasteRangeConnections` — paste destination can extend the grid
+- `AddSheetConnections` — adds a new sheet. Default grid is 1000 × 26 = 26,000 cells, enough to trip the limit on a near-full spreadsheet
+
+**Legacy activities**:
+- `WriteCell`, `WriteRange`, `AppendRow` — same auto-expand triggers as the modern variants
+- `AddNewSheet` — same 26,000-cell default grid as `AddSheetConnections`
+- `AddDeleteColumns` (in *Add* mode), `AddDeleteRows` (in *Add* mode) — explicitly add N columns/rows to the grid
+- `AutoFillRange`, `CopyPasteRange` — same expand triggers as the modern variants
+- `CopySheet` ⚠️ — duplicates an entire sheet's cell grid in one shot; the most aggressive trigger and a **legacy-only** failure mode (no modern `*Connections` equivalent)
+- `BatchUpdateValuesScope` — scope wrapper; the error reaches the user from this scope when one of the inner writes expands past the cap
+
+What can cause it:
+- The target spreadsheet is at or near Google's hard cap of 10,000,000 cells, and the activity issues a write or expand operation that would push it over. The cell count is the sum across all sheets in the spreadsheet, where each sheet's cell count is the rows × columns of its **bounded grid** — even empty cells inside the grid count.
+- This is a hard Google Sheets quota and **cannot be raised** by the user, the workspace plan, or UiPath. The only path forward is to reduce the spreadsheet's cell count.
+
+## Resolution
+
+The error is unambiguous; no further investigation is needed. Stop the investigation and ask the user to free cells in the target spreadsheet before running the workflow again:
+
+1. **Delete unused sheets** — every sheet (tab), even an empty one, contributes its full bounded grid to the total. Removing one default-sized sheet recovers 26,000 cells.
+2. **Trim oversized grids** — sheets often have many empty rows or columns extending the bounded grid past the actual data. Resize the grid (delete trailing empty rows/columns) to drop the cell count without losing content.
+3. **Archive into a new spreadsheet** — move historical sheets into a separate spreadsheet so the active one stays under the cap. This is the right answer when the data genuinely needs all those cells.
+4. **Do not retry the workflow** until the user confirms cells have been freed. Re-running against a still-at-cap spreadsheet will produce the same exception.
+
+If the activity in evidence is `BatchUpdateValuesScope`, identify which inner write triggered the expansion (the scope's failure message includes the offending range) — the resolution still applies to the spreadsheet as a whole, not to the scope.

package/skills/uipath-troubleshoot/references/activity-packages/gsuite-activities/playbooks/sheets-invalid-range.md

@@ -0,0 +1,51 @@
+---
+confidence: medium
+---
+
+# GSuite Sheets — Invalid range / unable to parse range
+
+## Context
+
+What this looks like — `GSuiteException` carrying a Google Sheets API 400 BadRequest:
+
+`The service sheets has thrown an exception. HttpStatusCode is BadRequest. Invalid data[0]: Unable to parse range: <SheetName>!<CellRef>`
+
+Common observed forms of `<CellRef>`:
+- `A0`, `B0`, etc. — invalid row index (Sheets is 1-indexed; there is no row 0)
+- empty string after the `!` — missing cell reference
+- malformed column (e.g., special characters, lowercase letters mixed with numbers in invalid positions)
+- bare cell with no sheet name on a multi-sheet spreadsheet
+
+What activities can produce this error — any Sheets activity that takes a range or cell address in A1 notation, including:
+
+**Modern activities**: `ReadCellConnections`, `ReadRangeConnections`, `ReadRowConnections`, `ReadColumnConnections`, `WriteCellConnections`, `WriteRangeConnections`, `WriteRowConnections`, `WriteColumnConnections`, `AutoFillRangeConnections`, `CopyPasteRangeConnections`, `DeleteRangeConnections`, `ForEachRowConnections`, `SetRangeColorConnections`, `GetCellColorConnections`.
+
+**Legacy activities**: `ReadCell`, `ReadRange`, `ReadRow`, `ReadColumn`, `WriteCell`, `WriteRange`, `AutoFillRange`, `CopyPasteRange`, `ClearRange`, `DeleteRange`, `ForEachSheetRow`, `GetCellColor`.
+
+What can cause it — Google's Sheets API rejected the supplied range string. Several possible causes:
+- **1-indexing mistake** — the workflow references row `0` (e.g., `A0`, `Sheet1!A0`); Sheets row indices start at `1`. Most common when the range is built by string concatenation from a 0-based loop counter.
+- **Empty or partial range** — the cell portion after `!` is empty, or the variable holding the range was null/empty at runtime.
+- **Sheet name with special characters not quoted** — sheet names containing spaces, apostrophes, or non-ASCII characters require single quotes around the sheet name in A1 notation (e.g., `'Q1 2026'!A1`, not `Q1 2026!A1`).
+- **Stale sheet reference** — the sheet was renamed or deleted after the workflow was authored, and the configured range still uses the old name.
+- **Off-by-one in dynamic construction** — a variable used to build the cell address produced an out-of-bounds value (negative, zero, or extreme number).
+
+## Investigation
+
+1. From the workflow source, capture the exact range/cell expression configured on the activity and identify whether it is a literal string or a dynamic expression.
+2. From the error message, extract the `<SheetName>!<CellRef>` portion — Google echoes back the exact range it failed to parse, so this is the authoritative input value at runtime.
+3. Match the failed range against the cause list above:
+   - Ends in `0` (e.g., `A0`) → 1-indexing mistake
+   - Empty or just `!` after the sheet name → null/empty variable
+   - Sheet name has spaces or special characters and is not single-quoted → quoting issue
+   - Sheet name doesn't exist in the target spreadsheet → stale reference
+4. If the range is dynamic, trace the upstream variable assignments to find where the bad value was produced.
+
+## Resolution
+
+- **1-indexing mistake**: change the row index to start at `1`. If the value comes from a loop counter, add `1` to the counter when building the address (or change the loop to start from `1`).
+- **Empty/null range**: add a guard before the activity that fails the workflow with a clear message when the range variable is null/empty, rather than letting it reach the API.
+- **Sheet name quoting**: wrap the sheet name in single quotes when it contains spaces or special characters: `'My Sheet'!A1`. The activity does not auto-quote.
+- **Stale reference**: update the configured sheet name to match the spreadsheet's current sheet titles. Use `ForEachSheetConnections` or open the spreadsheet to confirm the actual sheet names.
+- **Dynamic construction**: ensure the variable that builds the cell address is bounded (positive integer ≥ 1) and validated before use.
+
+If the configured range is a literal that looks correct and the spreadsheet's sheet names match, ask the user to copy the range as it appears in the failed run's job arguments — the runtime value may differ from the design-time expression.

package/skills/uipath-troubleshoot/references/activity-packages/gsuite-activities/playbooks/upload-storage-quota-exceeded.md

@@ -0,0 +1,40 @@
+---
+confidence: high
+---
+
+# GSuite Upload — Drive storage quota or shared drive file limit exceeded
+
+## Context
+
+What this looks like — `GSuiteException` with the format `Upload failed after {bytesUploaded} bytes. {googleError}`. The `{googleError}` portion comes verbatim from the Google API and indicates a 403 quota condition. Common observed forms:
+
+- `Upload failed after 0 bytes. The service drive has thrown an exception. HttpStatusCode is Forbidden. The file limit for this shared drive has been exceeded.`
+- `Upload failed after 0 bytes. Google.Apis.Requests.RequestError`
+  `The user's Drive storage quota has been exceeded. [403]`
+  `Errors [`
+  `Message[The user's Drive storage quota has been exceeded.] Location[ - ] Reason[storageQuotaExceeded] Domain[usageLimits]`
+  `]`
+
+`bytesUploaded` is typically `0` when the limit is exceeded before the upload starts, but can be non-zero if the limit is hit mid-upload.
+
+What activities can produce this error:
+- **Drive uploads** — `UploadFilesConnections` (modern), legacy `UploadFile`
+- **Gmail attachment uploads** — `SendEmailConnections`, `ReplyToEmailConnections`, `ForwardEmailConnections` when the email carries an attachment large enough to require a multipart upload
+
+What can cause it — two underlying quota conditions, both surfaced as Google 403:
+- **`storageQuotaExceeded`** — the authenticated user's Drive storage is full. Applies to the entire account quota (free tier, Workspace plan storage, or pooled storage).
+- **Shared drive file count limit** — the destination shared drive has hit Google's hard limit of items it can hold (currently 500,000). Typical wording: `The file limit for this shared drive has been exceeded.` Bytes do not matter here — every file/folder counts toward the limit, including trashed items not yet permanently deleted.
+
+These are the only two causes that can produce the messages above. They are not transient and will not resolve themselves on retry.
+
+## Resolution
+
+The error is unambiguous; no further investigation is needed. The storage is full. Stop the investigation and ask the user to free space (or escalate the quota) before running the workflow again:
+
+1. **Confirm which limit was hit** by reading the Google error portion of the message:
+   - `storageQuotaExceeded` / `The user's Drive storage quota has been exceeded.` → user account storage is full
+   - `The file limit for this shared drive has been exceeded.` → shared drive has hit the 500K item cap
+2. **Ask the user to make space:**
+   - For account storage: empty Drive Trash, delete or transfer-out large files, or upgrade the Google Workspace storage plan.
+   - For shared drive file limit: delete unused items from the shared drive (including emptying the shared drive Trash — trashed items still count), move items to a different shared drive, or split the workload across multiple shared drives.
+3. **Do not retry the workflow** until the user confirms space has been freed. Re-running against a still-full quota will produce the same exception.

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

@@ -0,0 +1,11 @@
+# Google Workspace Activities Presentation Rules
+
+- **Activities** — use the display name in prose (e.g., "Get Newest Email", "Add Sheet", "Create Folder"). Include the class name in parentheses on first mention so an agent can match a stack trace (e.g., "Get Newest Email (`GetNewestEmailConnections`)"). Don't lead with the fully qualified class name.
+- **Connections** — use the connection name as configured in Integration Service (e.g., "gsuiteactivities"), not internal IDs. When the underlying account matters for the diagnostic, also state the authenticated Google account email.
+- **Drive items (files / folders)** — refer to a Drive file or folder by its title with parent context (e.g., "folder 'Reports' under '/Projects/2024'"), not by raw Drive ID. Include the ID or URL only when the diagnostic requires it — for example, when the playbook is the 404 case and the ID itself is what failed to resolve.
+- **Spreadsheets** — refer to a spreadsheet by its title (e.g., "spreadsheet 'Q1 Forecast'"), not by spreadsheet ID. Show the URL/ID only when the user needs to open it or the ID itself is the subject of the error.
+- **Sheets (tabs inside a spreadsheet)** — refer to a sheet by its title (e.g., "sheet 'Data'"), not by `sheetId`. Name comparison for `Add Sheet` is case-insensitive — when reporting a conflict, show both the configured name and the existing sheet's title verbatim.
+- **Gmail folders / labels** — use the user-visible label name (e.g., "Inbox", "Sent", "label 'Customers/VIP'"), not the internal Gmail label ID (`Label_123`, `INBOX`, `SENT`). When reporting filter scope, include the configured `Folder` value as the user typed it.
+- **`ConflictResolution` 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").
+- **Local file paths (upload sources)** — show the full local path as configured on the activity (e.g., `C:\Reports\invoice.pdf`), not just the file name. Local paths and Drive paths look similar — clarify which one you mean.
+- **Shared drives** — distinguish "My Drive" (the user's personal Drive) from a shared drive, and refer to a shared drive by its display name (e.g., "shared drive 'Finance Ops'"), not by ID. Storage and file-count limits behave differently between the two.

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

@@ -0,0 +1,13 @@
+# Google Workspace Activities Playbooks
+
+**Investigation guide:** [investigation_guide.md](./investigation_guide.md) — data correlation rules and testing prerequisites for Google Workspace Activities investigations
+
+| Issue | Confidence | Description | Playbook |
+|-------|:---:|-------------|----------|
+| Get Newest Email — No Matching Email Found | High | Gmail mailbox contains zero messages matching the configured filter at the moment the activity runs (`GmailException: No email matching the search criteria has been found`) | [get-newest-email-not-found.md](./playbooks/get-newest-email-not-found.md) |
+| Drive — Name Conflict in Specified Folder | High | Drive activity (CreateFolder, CopyFile, MoveFile, Rename, Upload, CreateSpreadsheet, CreateDocument) throws `GSuiteException: Multiple items with the name <name> found in the specified folder.` because the configured `ConflictResolution` cannot resolve a duplicate name | [drive-multiple-items-name-conflict.md](./playbooks/drive-multiple-items-name-conflict.md) |
+| Add Sheet — Sheet Name Already Exists | High | Target spreadsheet already contains a sheet (tab) with the configured `SheetName` (case-insensitive) and `ConflictResolution = Fail` (`GSuiteException: A sheet with the same name already exists.`) | [add-sheet-name-conflict.md](./playbooks/add-sheet-name-conflict.md) |
+| Drive — File or Folder Not Found (404) | High | Drive activity fails to resolve the configured ID/URL/path because the resource was deleted, trashed, or is not accessible to the connection (`File not found: <id>. [404]` / `HttpStatusCode is NotFound` / `The resource was not found.`) | [drive-file-not-found.md](./playbooks/drive-file-not-found.md) |
+| Upload — Drive Storage Quota or Shared Drive File Limit Exceeded | High | Upload activity (Drive `UploadFilesConnections`, legacy `UploadFile`, or Gmail send/reply/forward with attachments) fails because the user's Drive storage is full (`storageQuotaExceeded`) or the destination shared drive has hit the 500K item limit (`Upload failed after <N> bytes. ...`) | [upload-storage-quota-exceeded.md](./playbooks/upload-storage-quota-exceeded.md) |
+| Sheets — 10 Million Cell Limit Exceeded | High | Sheets write/expand activity (Write Range/Cell/Row/Column, AutoFill, CopyPaste, Add Sheet, plus legacy AppendRow, CopySheet, BatchUpdateValuesScope, Add modes of AddDelete*) fails because the operation would push the spreadsheet past Google's 10M cell cap (`HttpStatusCode is BadRequest. This action would increase the number of cells in the workbook above the limit of 10000000 cells.`) | [sheets-cell-limit-exceeded.md](./playbooks/sheets-cell-limit-exceeded.md) |
+| Sheets — Invalid Range / Unable to Parse Range | Medium | Sheets read/write activity passes a malformed A1-notation range to the Sheets API (`HttpStatusCode is BadRequest. Invalid data[0]: Unable to parse range: <SheetName>!<CellRef>`). Common causes: 1-indexing mistake (row 0), empty/null range, unquoted sheet names with spaces, stale sheet references, off-by-one in dynamic construction | [sheets-invalid-range.md](./playbooks/sheets-invalid-range.md) |

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

@@ -0,0 +1,30 @@
+# Microsoft Office 365 Activities Investigation Guide
+
+## Data Correlation
+
+Before using any fetched data, verify it matches the user's reported problem:
+
+- **Activity** — the faulted activity's namespace and class match the reported failure (e.g., `UiPath.MicrosoftOffice365.Activities.Mail.MoveEmailConnections`). Modern connections activities and legacy activities (`MoveMail`, `DownloadFile`, `CreateFolder`, `UploadFile`, `CreateWorkbook`, `AddSheet`) sometimes share display names but run different code paths — treat them as different.
+- **Connection / Microsoft 365 account** — the Integration Service connection in evidence authenticates against the same Microsoft 365 user principal the user is asking about. Different connections = different mailboxes, different OneDrive scopes, different SharePoint sites = unrelated data.
+- **Mailbox in scope** — for Mail activities, confirm the resolved mailbox is the one the user is asking about. The same connection can target the user's own mailbox, a shared mailbox, or a delegated mailbox via the activity argument; Outlook IDs are mailbox-scoped, so an item that resolves in one mailbox will not resolve in another.
+- **Target resource** — the resource identifier in evidence matches the one the user reports: mail folder ID or path, message ID, OneDrive/SharePoint item ID or URL or drive-relative path, drive ID, SharePoint site URL plus document library, workbook file name, sheet name. Don't substitute a similarly-named resource.
+- **Workflow file** — if the project contains multiple workflows, the error originates from the workflow the user is asking about, not a different `.xaml` / `.cs` that happens to use the same activity.
+- **Timestamp** — the failure occurred during the time window the user reported. Load-bearing for filter-based Mail activities (only messages received at or before the run time are eligible), and for any investigation where the user may have moved, renamed, or deleted the target resource between runs.
+
+If the data doesn't match: **discard it**. Do NOT use unrelated data as a proxy. Report the mismatch and ask for clarification.
+
+## Domain-Specific Data Gathering
+
+1. **Activity execution traces** — these activities emit per-call traces. Pull them when available — they expose the exact Microsoft Graph endpoint hit, request/response status, and timing. Trace evidence narrows whether the failure originated at connection resolution, OAuth token validation, the Graph call, or post-processing inside the activity.
+
+## Testing Prerequisites
+
+When testing hypotheses for Microsoft Office 365 Activities issues, gather and verify these before drawing conclusions:
+
+1. **Activity identity** — capture both the class name and the display name from the workflow source or stack trace. Distinguish modern `*Connections` activities from legacy equivalents.
+2. **Target Microsoft 365 service** — identify whether the call lands on Outlook (Mail), OneDrive, SharePoint document libraries, Excel, Outlook Calendar, or SharePoint Lists. The same Microsoft Graph status code (404 / 403 / 409) surfaces with different wording and different remediation per service.
+3. **Connection target** — capture the Integration Service connection name and the underlying Microsoft 365 user principal name (UPN) it authenticates as. For shared mailbox or SharePoint operations, also capture which mailbox / site / document library is in scope.
+4. **Activity input properties** — capture every input property the activity uses to address its target, from the workflow source (not from a summary): filter collections, `ConflictBehavior` / `ConflictResolution`, `MailFolder` argument (ID or path), `CreateFolderIfMissing`, target identifiers (ID / URL / path / browse selection), `UseDriveCard` / `DriveId`, source local paths, attachment names. The playbook the agent is following will name the subset that matters.
+5. **Mailbox / drive resolution evidence** — for Mail activities, capture the `Account` argument value and the resolved mailbox UPN. For Files activities, capture the resolved `DriveId` plus, for SharePoint, the site URL and document library name. Failures one tier above the item (drive-not-found, site-not-found, shared-item-not-found) are diagnosed differently from item-not-found.
+6. **Job run timestamp** — exact time the activity executed. Required for filter-based Mail investigations (mailbox state at run time), for trigger debug/healing sample replays, and for any investigation where the target resource may have been deleted, moved, or renamed between authoring and execution.
+7. **Package version** — `UiPath.MicrosoftOffice365.Activities` version. Behavior, exception messages, supported `ConflictBehavior` / `ConflictResolution` values, and the wrapping form of resource-not-found errors have shifted across versions; version-specific bugs are documented in playbooks as they're discovered.

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

@@ -0,0 +1,55 @@
+# Microsoft Office 365 Activities
+
+Activities from the `UiPath.MicrosoftOffice365.Activities` package for automating Microsoft 365 services covered by current diagnostics: Outlook (Mail), OneDrive and SharePoint document libraries (Files), and Excel. Modern activities call Microsoft Graph through OAuth-authenticated connections managed by Integration Service; legacy XAML activities use an Office 365 application-scope container (Windows only).
+
+## How Connections Work
+
+When a modern activity executes, it:
+
+1. Resolves the configured Integration Service connection to obtain an OAuth access token
+2. Issues a Microsoft Graph REST API request (Outlook, OneDrive, SharePoint, or Excel)
+3. Maps the Graph response back into the activity output, or throws on error
+
+Failures can originate at any of those layers — connection resolution (Integration Service), token validation (Microsoft Identity), the Graph call itself, or post-processing inside the activity. Knowing which layer produced the error narrows the investigation.
+
+## Key Activity Types
+
+### Mail (Outlook)
+
+- **Get Newest Email** (`GetNewestEmail`) — retrieves the single most recent message matching a configured filter from a configured mail folder.
+- **Folder-scoped read activities** (`GetEmailListConnections`, `ForEachEmailConnections`, plus the persistence and trigger pair `WaitForEmailReceived` / `NewEmailReceived`, and the outbound pair `WaitForEmailSent` / `EmailSent`) — read or wait for messages in a configured mail folder; folder is resolved by ID, path, or browse selection.
+- **Move Email** (`MoveEmailConnections`, legacy `MoveMail`) — move a message into a destination mail folder selected by ID or by path. `MoveEmailConnections` exposes `CreateFolderIfMissing` for path-based input.
+- **Download operations** (`DownloadEmailConnections`, `DownloadEmailAttachments`) — write a message body or its attachments to a local destination folder; behavior on duplicate local filename is governed by the `ConflictBehavior` enum (`Replace`, `Fail`, `Rename`).
+
+### Files (OneDrive / SharePoint)
+
+- **Item write operations** (`CreateFolderConnections`, `CopyItemConnections`, `MoveItemConnections`, `RenameItemConnections`, `UploadFilesConnections`, plus legacy `CreateFolder` and `UploadFile`) — create, copy, move, rename, or upload Drive items; behavior on duplicate name in the destination is governed by the `ConflictBehavior` enum (`Replace`, `Fail`, `Rename`).
+- **Item resolution by ID, URL, path, or browse selection** (most Files activities, e.g., `GetFileFolderConnections`, `GetFileFolderMetadataConnections`, `GetFileListConnections`, `DownloadFileConnections`, `DeleteItemConnections`, `ShareItemConnections`, `UpdateFileFolderMetadataConnections`, `CheckinCheckoutFileConnections`, `ForEachFileFolderConnections`, `AssignSensitivityLabelConnections`, `GetSensitivityLabelsConnections`, persistence `WaitForFileCreated` / `WaitForFileUpdated`, plus the write operations above) — resolve a target Drive item against Microsoft Graph.
+- **Download File** (`DownloadFileConnections`, legacy `DownloadFile`, legacy `ExportAsPdf`) — write a Drive item to a local destination; behavior on duplicate local filename is governed by `ConflictResolution`.
+
+### Excel
+
+- **Create Workbook** (`CreateWorkbookConnections`, legacy `CreateWorkbook`) — create a new `.xlsx` in OneDrive or a SharePoint document library; behavior on duplicate workbook name is governed by `ConflictBehavior`.
+- **Sheet operations** (`AddSheetConnections`, `RenameSheetConnections`, legacy `AddSheet`) — add or rename a sheet (tab) inside a workbook; `AddSheetConnections` honors `ConflictBehavior` on duplicate sheet name.
+
+## Common Failure Patterns
+
+### Mail
+
+- **Filter returns no matching email** — Mailbox contains zero messages matching the configured filter at the moment the activity runs. `Get Newest Email` throws `Office365Exception: No email matching the filter criteria, received in the last 1 hour has been found...` synchronously.
+- **Mail folder not found** — Mail activity (`MoveEmailConnections`, `GetNewestEmail`, `GetEmailListConnections`, `ForEachEmailConnections`, `WaitForEmailReceived`, `NewEmailReceived` trigger, legacy `MoveMail`) cannot resolve the configured `MailFolder`. Surfaces as one of: `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>.`.
+- **Local-filesystem name conflict on download** — `DownloadEmailConnections` or `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 because two attachments on the same email resolve to the same local filename. Conflict is on the local filesystem, not in OneDrive/SharePoint.
+
+### Files (OneDrive / SharePoint)
+
+- **404 — file or folder not found** — Files activity fails to resolve the configured ID, URL, path, or browse selection because the Drive item was deleted, moved out of scope, or is not accessible to the connection. Surfaces as `Office365Exception: The resource could not be found.` or as the wrapping form `Cannot find item configured with connection <connection> at path <path>.`
+- **Item name already exists** — Files write activity (`CreateFolderConnections`, `CopyItemConnections`, `MoveItemConnections`, `RenameItemConnections`, `UploadFilesConnections`) throws `Office365Exception: The specified item name already exists.` when the destination already contains an item with the target name and `ConflictBehavior = Fail`. Affects legacy activities equivalents as well (`CreateFolder`, `UploadFile`).
+- **Local-filesystem name conflict on download** — `DownloadFileConnections` throws `Office365Exception: Multiple items with the name <name> found in the specified folder.` when the **local** destination folder already contains a file with that name and `ConflictResolution = Fail`. Conflict is on the local filesystem, not in OneDrive/SharePoint.
+
+### Excel
+
+- **Workbook or sheet name already exists** — `CreateWorkbookConnections`, `AddSheetConnections`, or `RenameSheetConnections` throws `Office365Exception: The specified item name already exists.` when the target workbook or sheet name collides and `ConflictBehavior = Fail`. Affects legacy `CreateWorkbook` and `AddSheet` as well.
+
+## Package
+
+NuGet: `UiPath.MicrosoftOffice365.Activities`

package/skills/uipath-troubleshoot/references/activity-packages/o365-activities/playbooks/download-multiple-items-name-conflict.md

@@ -0,0 +1,37 @@
+---
+confidence: high
+---
+
+# O365 — Multiple items with the same name in the specified local folder
+
+## Context
+
+What this looks like:
+- A download activity from `UiPath.MicrosoftOffice365.Activities` throws `Office365Exception`
+- Error message: `Multiple items with the name <name> found in the specified folder.`
+- Job faults synchronously the moment the activity runs
+
+What activities can produce this error:
+- **Download Email** (`DownloadEmailConnections`) — `ConflictResolution = Fail` and the **local** destination folder already contains a file with the target email's filename
+- **Download File** (`DownloadFileConnections`) — `ConflictResolution = Fail` and the **local** destination folder already contains a file with the target file's name
+- **Download Email Attachments** (`DownloadEmailAttachments`) — either:
+  - `ConflictResolution = Fail` and the **local** destination folder already contains a file with one of the attachment names, OR
+  - two or more attachments on the same email resolve to the same local destination filename
+
+What can cause it:
+- The **local** destination folder already contains a file with the same name as the file being written, and `ConflictResolution` is `Fail`. 
+- For `DownloadEmailAttachments` only: two or more attachments on the same email share a filename (case-insensitive), so even an empty destination folder would end up with duplicates. With `ConflictResolution = Fail`, the activity detects this and throws before writing anything.
+
+> **Conflict is on the local filesystem, not in OneDrive/SharePoint.** The wording "in the specified folder" refers to the **local** destination folder configured on the activity — not a remote Microsoft Graph location.
+>
+> **Different message, related cause:** when the conflict is on the **remote** OneDrive/SharePoint/Excel side (Create Folder, Copy/Move/Rename Item, Upload Files, Create Workbook, Add Sheet, Rename Sheet), the activity throws `The specified item name already exists.` instead. See [item-name-already-exists.md](./item-name-already-exists.md).
+
+## Resolution
+
+The error is unambiguous; no further investigation is needed. Stop the investigation and ask the user to do one of the following:
+
+1. **Change the destination filename** so it is unique within the local destination folder (for `DownloadEmailConnections` and `DownloadFileConnections`, this means changing the file name in `Destination path`; for `DownloadEmailAttachments`, the attachment names are dictated by the email and cannot be changed — use option 2 or 3).
+2. **Ensure the local destination folder contains no file with that name** — delete, rename, or move the existing file before re-running the workflow.
+3. **Change the `ConflictResolution(conflict behavior)`** on the activity to a value that handles the duplicate:
+   - `Rename` — automatically rename the new file to a unique name. For `DownloadEmailAttachments`, this also handles the genuine multiple-attachments-with-the-same-name case.
+   - `Replace` — overwrite the existing local file.

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

@@ -0,0 +1,59 @@
+---
+confidence: high
+---
+
+# O365 Drive — File or folder not found
+
+## Context
+
+What this looks like — any of the following message patterns, all originating from Microsoft Graph returning `ItemNotFound` (HTTP 404) for a OneDrive/SharePoint resource:
+
+- `The resource could not be found.` 
+- `Cannot find item configured with connection <connection> at path <path>.` 
+- `Cannot find item configured with connection <connection>.` 
+- `A file with the specified ID does not exist.`
+
+The job faults synchronously the moment the activity tries to resolve the OneDrive/SharePoint resource.
+
+What activities can produce this error:
+- **Get File/Folder** (`GetFileFolderConnections`), **Get File/Folder Metadata** (`GetFileFolderMetadataConnections`), **Get File List** (`GetFileListConnections`) — when the configured `Item` (ID, URL, path, or browse selection) doesn't resolve.
+- **Download File** (`DownloadFileConnections`) — when the source `Item` doesn't resolve.
+- **Move Item** (`MoveItemConnections`), **Copy Item** (`CopyItemConnections`) — when either the source `Item` or the destination `Folder` doesn't resolve.
+- **Rename Item** (`RenameItemConnections`) — when the target `Item` doesn't resolve.
+- **Delete Item** (`DeleteItemConnections`) — when the target `Item` doesn't resolve.
+- **Share Item** (`ShareItemConnections`) — when the target `Item` doesn't resolve.
+- **Update File/Folder Metadata** (`UpdateFileFolderMetadataConnections`) — when the target `Item` doesn't resolve.
+- **Create Folder** (`CreateFolderConnections`) — when the configured parent `Folder` doesn't resolve.
+- **Upload Files** (`UploadFilesConnections`) — when the destination parent `Folder` doesn't resolve.
+- **For Each File/Folder** (`ForEachFileFolderConnections`) — when the parent `Folder` doesn't resolve.
+- **Check In/Out File** (`CheckinCheckoutFileConnections`) — when the target `File` doesn't resolve.
+- **Assign Sensitivity Label** (`AssignSensitivityLabelConnections`), **Get Sensitivity Labels** (`GetSensitivityLabelsConnections`) — when the target `Item` doesn't resolve.
+- **Wait For File Created** / **Wait For File Updated** (persistence triggers) — when the watched parent `Folder` doesn't resolve.
+- Legacy activities: `DownloadFile`, `ExportAsPdf`, and other files activities that take a `DriveItem` argument.
+
+What can cause it:
+- **Item no longer exists.** The configured ID, URL, path, or browse selection points to a OneDrive/SharePoint item that has been deleted, moved to the recycle bin, or permanently removed. Graph authoritatively returns 404.
+- **Stale ID after move/restore.** OneDrive/SharePoint item IDs are mostly durable but can change after a cross-drive move, after a restore from the recycle bin to a different location, or after re-provisioning of the user's OneDrive. An ID captured from a previous run may stop resolving even though the file is visible in the UI.
+- **Wrong drive in scope.** The item exists, but in a different drive (a different user's OneDrive, a different SharePoint document library, or a different shared drive) than the one the activity targets. Graph returns 404 because the item ID is scoped to the wrong drive.
+- **SharePoint document library / drive name mismatch.** The configured drive name does not match an accessible drive on the SharePoint site. This surfaces as `You do not have access to any Drives named '<name>' inside SharePoint site '<siteUrl>'.`, which is the drive-level analog of this error. The site itself may also not exist (`The specified site <site> does not exist.`).
+- **Shared link no longer valid.** The configured shared URL has been revoked, the sharing scope changed, or the link points to an item the connection cannot read. Surfaces as `The specified shared item does not exist.` or as the standard `The resource could not be found.`
+- **Path-segment mismatch.** Path-based input is case-insensitive but otherwise exact. Trailing whitespace, mismatched separators, an item renamed since the path was authored, or a path that crosses drive roots will all miss.
+- **Insufficient scope.** The connection lacks `Files.Read.All` / `Files.ReadWrite.All` / `Sites.Read.All` / `Sites.ReadWrite.All` for the target resource. Graph can return 404 instead of 403 for cross-tenant or delegated access where the connection cannot enumerate the parent.
+- **Folder passed where file is required.** For `DownloadFileConnections` and the legacy `DownloadFile` / `ExportAsPdf`, passing a `DriveItem` that represents a folder produces `A file with the specified ID does not exist.` This is a configuration mistake, not a missing remote resource.
+
+> **Different cause, do not apply this playbook:**
+> - `FileFolderExistsConnections` does **not** surface this error. If the user reports a fault from this activity, the cause is something other than item-not-found.
+> - `The resource could not be found.` raised by a **Mail** activity (e.g., `MarkAsReadUnreadConnections`, `DeleteEmailConnections`, `MoveEmailConnections`) is a missing message or mail folder, not a Drive item. See [mail-folder-not-found.md](./mail-folder-not-found.md) for the mail-folder case.
+
+## Resolution
+
+The error is unambiguous; no further investigation is needed. Stop the investigation and ask the user to verify the target resource:
+
+1. **Confirm the file or folder still exists** at the expected location in OneDrive / SharePoint. Check the recycle bin — a recently deleted item is the most common cause. A restore from the recycle bin can change the item ID; if the user has a stored ID from before the delete, it will not resolve.
+2. **Confirm the configured identifier is correct** — the `Item` argument on the activity must match what's currently in OneDrive/SharePoint. For ID input, the ID must come from the same drive the activity targets. For path input, paths are case-insensitive but otherwise exact: trailing whitespace, mismatched separators, or a renamed segment all cause this error. For browse-card input, ensure the bound resource hasn't been moved out of the original parent.
+3. **Confirm the resolved drive/site** is the one the user expects. `UseDriveCard` selections may bind to a different drive than intended (e.g., the user's personal OneDrive vs. a SharePoint document library). For SharePoint, also confirm the site URL and document library name.
+4. **Confirm the connection's authenticated account has access** to the resource. A file owned by another user that was never shared with this account, an item in a SharePoint site the connection's account isn't a member of, or a shared link with revoked access will all surface as 404.
+5. **Confirm the connection's scopes.** `Files.Read.All` (or `Files.ReadWrite.All`) is required for OneDrive operations; `Sites.Read.All` (or `Sites.ReadWrite.All`) is required for SharePoint operations. Missing scopes can surface as 404 on enumeration even when the resource physically exists.
+6. **For `DownloadFileConnections` failing with `A file with the specified ID does not exist.`**, the configured `Item` is a folder, not a file. Ask the user to point the activity at a file, or to use `ForEachFileFolderConnections` followed by a per-file download.
+
+If the user confirms the resource exists in the Drive UI under the resolved account, the connection has the required scopes, and the identifier is correct, the cause is outside the activity — escalate (tenant-level permissions, conditional access, sharing inheritance, or a Graph-side delay after a recent move/rename) rather than continue under this playbook.

package/skills/uipath-troubleshoot/references/activity-packages/o365-activities/playbooks/get-newest-email-no-match.md

@@ -0,0 +1,34 @@
+---
+confidence: high
+---
+
+# O365 Get Newest Email — no email matched the filter criteria
+
+## Context
+
+What this looks like:
+- Activity `Get Newest Email` (UiPath.MicrosoftOffice365.Activities, `GetNewestEmail`) throws `Office365Exception`
+- Error message: `No email matching the filter criteria, received in the last 1 hour has been found. Please generate a new email that fits the criteria and run the workflow again`
+- Job faults synchronously the moment the activity runs — no retry, no wait
+
+What can cause it:
+- The target mailbox contains zero messages matching the configured filter at the moment the activity executes. This is the only cause — the activity issues a single Microsoft Graph query and throws when the result is empty.
+
+What to look for:
+- The exact filter the activity was configured with: `MailFolder` (Inbox or selected folder), `FreeTextFilter` (free-text search), `QueryFilter` (raw OData `$filter` expression), `Importance` (Any/Low/Normal/High), `Mailbox` (shared mailbox address, when `UseSharedMailbox = true`)
+- Boolean modifiers tightening the search: `UnreadOnly`, `WithAttachmentsOnly`
+- The job run timestamp — only emails received at or before this moment are eligible
+
+> The same exception can also surface from `WaitForEmailReceived` (persistence) and the `NewEmailReceived` trigger when their debug/healing sample lookup returns empty. The diagnostic is the same — verify the mailbox against the filter — but those activities are async by design, so do not apply this playbook's "synchronous fault on first run" framing to them.
+
+## Investigation
+
+1. From the job logs or workflow, capture the exact values of every filter property listed above and the job start timestamp.
+2. Confirm the activity is `GetNewestEmail` (display name "Get Newest Email") in `UiPath.MicrosoftOffice365.Activities` — not a trigger or persistence activity, which have different semantics.
+3. There is nothing further to verify programmatically; the Microsoft Graph API has already authoritatively returned zero matches for that query. Proceed to Resolution.
+
+## Resolution
+
+- **In all cases:** Report the captured filter values and job timestamp to the user and ask them to sign in to the target mailbox (or shared mailbox, if `UseSharedMailbox = true`) and confirm whether any message matching those filters was received **at or before** the job run timestamp. Then:
+  - **If no matching email existed in the mailbox at that time:** This is expected behavior, not a defect. Recommend either (a) loosening the filter (clear `UnreadOnly`/`WithAttachmentsOnly`, broaden `FreeTextFilter`, simplify the `QueryFilter` OData expression, set `Importance` to `Any`, switch `MailFolder` to a broader folder such as Inbox), or (b) wrapping the activity in a Try/Catch so the workflow handles the empty-result case explicitly, or (c) scheduling the job to run after the expected email arrives.
+  - **If a matching email did exist in the mailbox at that time:** Ask the user to copy the matching message's relevant headers (From, To, Subject, ReceivedDateTime, Importance, IsRead, HasAttachments, parent folder) and compare them against the activity's configured filter to identify the mismatch (common culprits: `MailFolder` set to a subfolder that excludes the message, OData `$filter` syntax error or wrong property name in `QueryFilter`, `FreeTextFilter` case/punctuation expectations Graph search does not honor, `Importance` set to a specific level when the email is `Normal`, time-zone offset on date predicates).

package/skills/uipath-troubleshoot/references/activity-packages/o365-activities/playbooks/item-name-already-exists.md

@@ -0,0 +1,38 @@
+---
+confidence: high
+---
+
+# O365 — The specified item name already exists
+
+## Context
+
+What this looks like:
+- An activity from `UiPath.MicrosoftOffice365.Activities` throws `Office365Exception`
+- Error message: `The specified item name already exists.`
+- Job faults synchronously the moment the activity runs
+
+What activities can produce this error:
+- **Create Folder** (`CreateFolderConnections`) — folder with that name already exists in the destination and `ConflictBehavior = Fail`
+- **Copy Item** (`CopyItemConnections`) — destination already contains an item with the target name and `ConflictBehavior = Fail`
+- **Move Item** (`MoveItemConnections`) — destination already contains an item with the target name and `ConflictBehavior = Fail`
+- **Rename Item** (`RenameItemConnections`) — an item with the new name already exists in the same parent
+- **Upload Files** (`UploadFilesConnections`) — destination already contains an item with the target name and `ConflictBehavior = Fail`
+- **Create Workbook** (`CreateWorkbookConnections`) — a workbook with that name already exists in the destination and `ConflictBehavior = Fail`
+- **Add Sheet** (`AddSheetConnections`) — target workbook already contains a sheet with that name and `ConflictBehavior = Fail`
+- **Rename Sheet** (`RenameSheetConnections`) — a sheet with the new name already exists in the workbook
+- Legacy activities equivalents: `CreateFolder`, `UploadFile`, `CreateWorkbook`, `AddSheet`
+
+What can cause it:
+- The destination already contains an item (folder, file, workbook, or sheet) with the same name as the new/target item, and the configured `ConflictBehavior` is `Fail`.
+
+## Resolution
+
+The error is unambiguous; no further investigation is needed. Stop the investigation and ask the user to do one of the following:
+
+1. **Change the name** of the new/target item (e.g., `FolderName`, `NewName`, `WorkbookName`, `SheetName`) so it is unique within the destination.
+2. **Ensure the destination contains no item with that name** — rename, delete, or move the existing folder/file/workbook/sheet before re-running the workflow.
+3. **Change the `ConflictBehavior`** on the activity to a value that handles the duplicate:
+   - `Rename` — automatically rename the new item to a unique name
+   - `Replace` — replace the existing item
+
+   `Fail` is the value that surfaces this error. `RenameItemConnections` and `RenameSheetConnections` operate on existing items and do not expose the full enum — for those, only options 1 and 2 apply.