From 3c7513cd007a29b42f20bbc1e30e39c153bc287b Mon Sep 17 00:00:00 2001 From: Dan Morosanu Date: Mon, 3 Aug 2026 13:28:13 +0300 Subject: [PATCH] fix(troubleshoot): re-anchor prompt fault timing to the run so frozen fixtures stop drifting --- .../classic-click-noop-simulate/task.yaml | 7 ++++--- .../classic-typeinto-field-not-cleared/task.yaml | 7 ++++--- .../excel-delete-range-invalid-syntax/task.yaml | 4 ++-- .../activity-packages/excel-rr-sheet-case/task.yaml | 4 ++-- .../excel-scope-orphan-process-lock/task.yaml | 2 +- .../excel-write-range-formula-prefix/task.yaml | 2 +- .../task.yaml | 2 +- .../uia-browser-communication-failed/task.yaml | 7 ++++--- .../uia-click-noop-simulate-tech/task.yaml | 7 ++++--- .../rpa-is-connection-not-authorized-cns/task.yaml | 2 +- .../credential-store-unavailable/task.yaml | 2 +- .../logon-failure-password-mismatch/RESOLUTION.md | 2 +- .../logon-failure-password-mismatch/task.yaml | 10 +++++----- .../orchestrator/queue-items-failing-test/task.yaml | 2 +- .../rpa-consecutive-system-exceptions/task.yaml | 2 +- .../rpa-executor-service-disconnect/task.yaml | 2 +- .../orchestrator/rpa-serverless-robot-units/task.yaml | 2 +- 17 files changed, 35 insertions(+), 31 deletions(-) diff --git a/tests/tasks/uipath-troubleshoot/activity-packages/classic-click-noop-simulate/task.yaml b/tests/tasks/uipath-troubleshoot/activity-packages/classic-click-noop-simulate/task.yaml index 8078209867..085880ff0e 100644 --- a/tests/tasks/uipath-troubleshoot/activity-packages/classic-click-noop-simulate/task.yaml +++ b/tests/tasks/uipath-troubleshoot/activity-packages/classic-click-noop-simulate/task.yaml @@ -41,9 +41,10 @@ reference: file: RESOLUTION.md initial_prompt: | - My ClassicClaimsSubmit job in folder Finance finished Successful last night, - but it never clicked the Submit button in our Java claims app — the claim - stayed in Draft. There was no error at all. Why did it silently do nothing? + My ClassicClaimsSubmit job in folder Finance finished Successful on its + most recent run, but it never clicked the Submit button in our Java claims + app — the claim stayed in Draft. There was no error at all. Why did it + silently do nothing? success_criteria: - type: skill_triggered diff --git a/tests/tasks/uipath-troubleshoot/activity-packages/classic-typeinto-field-not-cleared/task.yaml b/tests/tasks/uipath-troubleshoot/activity-packages/classic-typeinto-field-not-cleared/task.yaml index 70c26f9b34..948ea5b91f 100644 --- a/tests/tasks/uipath-troubleshoot/activity-packages/classic-typeinto-field-not-cleared/task.yaml +++ b/tests/tasks/uipath-troubleshoot/activity-packages/classic-typeinto-field-not-cleared/task.yaml @@ -41,9 +41,10 @@ reference: file: RESOLUTION.md initial_prompt: | - My VendorOnboarding job in folder Finance finished Successful last night, but - the bank account number it wrote to the vendor record is wrong — it does not - match the value we gave it, and there was no error at all. Why? + My VendorOnboarding job in folder Finance finished Successful on its most + recent run, but the bank account number it wrote to the vendor record is + wrong — it does not match the value we gave it, and there was no error at + all. Why? success_criteria: - type: skill_triggered diff --git a/tests/tasks/uipath-troubleshoot/activity-packages/excel-delete-range-invalid-syntax/task.yaml b/tests/tasks/uipath-troubleshoot/activity-packages/excel-delete-range-invalid-syntax/task.yaml index 6705b5ef6e..e492176024 100644 --- a/tests/tasks/uipath-troubleshoot/activity-packages/excel-delete-range-invalid-syntax/task.yaml +++ b/tests/tasks/uipath-troubleshoot/activity-packages/excel-delete-range-invalid-syntax/task.yaml @@ -50,8 +50,8 @@ initial_prompt: | My Orchestrator job just faulted with `System.ArgumentException: The range is invalid`. Pinned job key: dd111111-cccc-dddd-eeee-ffffaaaabbbb. It's a Delete - Range activity and it worked yesterday when the workbook had data — - failed today on a freshly-recreated workbook. What's wrong? + Range activity and it worked on the previous run when the workbook had + data — then failed on a freshly-recreated workbook. What's wrong? success_criteria: - type: skill_triggered diff --git a/tests/tasks/uipath-troubleshoot/activity-packages/excel-rr-sheet-case/task.yaml b/tests/tasks/uipath-troubleshoot/activity-packages/excel-rr-sheet-case/task.yaml index 58efdabd4c..9a8adbed21 100644 --- a/tests/tasks/uipath-troubleshoot/activity-packages/excel-rr-sheet-case/task.yaml +++ b/tests/tasks/uipath-troubleshoot/activity-packages/excel-rr-sheet-case/task.yaml @@ -49,8 +49,8 @@ initial_prompt: | `UiPath.Excel.BusinessException: The sheet with the name 'data' does not exist.` Pinned job key: bb222222-7777-8888-9999-000011112222. The sheet DOES exist — I just opened the workbook and it's right there. The - same workflow worked yesterday on my dev machine. Why is the - Robot saying the sheet is missing? + same workflow worked on my dev machine. Why is the Robot saying + the sheet is missing? success_criteria: - type: skill_triggered diff --git a/tests/tasks/uipath-troubleshoot/activity-packages/excel-scope-orphan-process-lock/task.yaml b/tests/tasks/uipath-troubleshoot/activity-packages/excel-scope-orphan-process-lock/task.yaml index 70948878f4..083c1dba81 100644 --- a/tests/tasks/uipath-troubleshoot/activity-packages/excel-scope-orphan-process-lock/task.yaml +++ b/tests/tasks/uipath-troubleshoot/activity-packages/excel-scope-orphan-process-lock/task.yaml @@ -50,7 +50,7 @@ initial_prompt: | My Orchestrator job just faulted with `UiPath.Excel.BusinessException: Failed opening the Excel file. Possible reasons: file is corrupt, already used by another process or password protected.` Pinned job key: aa555555-cccc-dddd-eeee-ffffaaaabbbb. The file isn't - corrupt — it opened fine yesterday and there's no password on it. + corrupt — it opened fine on the previous run and there's no password on it. Why can't the robot open it now? success_criteria: diff --git a/tests/tasks/uipath-troubleshoot/activity-packages/excel-write-range-formula-prefix/task.yaml b/tests/tasks/uipath-troubleshoot/activity-packages/excel-write-range-formula-prefix/task.yaml index 11258b4aa0..a4ba1c3b8b 100644 --- a/tests/tasks/uipath-troubleshoot/activity-packages/excel-write-range-formula-prefix/task.yaml +++ b/tests/tasks/uipath-troubleshoot/activity-packages/excel-write-range-formula-prefix/task.yaml @@ -52,7 +52,7 @@ initial_prompt: | `System.Runtime.InteropServices.COMException (0x800A03EC): Application-defined or object-defined error.` Pinned job key: ee333333-cccc-dddd-eeee-ffffaaaabbbb. It's a Write Range writing 312 scraped HR records to a directory workbook. - Yesterday's run with the same workflow and same workbook + The previous run with the same workflow and same workbook succeeded. What changed? success_criteria: diff --git a/tests/tasks/uipath-troubleshoot/activity-packages/excel-write-range-uninitialized-datatable/task.yaml b/tests/tasks/uipath-troubleshoot/activity-packages/excel-write-range-uninitialized-datatable/task.yaml index 910e8d777a..41d0d79c5c 100644 --- a/tests/tasks/uipath-troubleshoot/activity-packages/excel-write-range-uninitialized-datatable/task.yaml +++ b/tests/tasks/uipath-troubleshoot/activity-packages/excel-write-range-uninitialized-datatable/task.yaml @@ -51,7 +51,7 @@ initial_prompt: | My Orchestrator job just faulted with `System.NullReferenceException: Object reference not set to an instance of an object.` Pinned job key: ee111111-cccc-dddd-eeee-ffffaaaabbbb. It's a Write - Range activity. Nothing in the workflow changed since yesterday's + Range activity. Nothing in the workflow changed since the previous successful run — what's wrong? success_criteria: diff --git a/tests/tasks/uipath-troubleshoot/activity-packages/uia-browser-communication-failed/task.yaml b/tests/tasks/uipath-troubleshoot/activity-packages/uia-browser-communication-failed/task.yaml index 2ec1045345..7f34dcae27 100644 --- a/tests/tasks/uipath-troubleshoot/activity-packages/uia-browser-communication-failed/task.yaml +++ b/tests/tasks/uipath-troubleshoot/activity-packages/uia-browser-communication-failed/task.yaml @@ -38,9 +38,10 @@ reference: file: RESOLUTION.md initial_prompt: | - My nightly CustomerHubSync job from folder Shared faulted last night on the - Use Browser step. It has run on the same schedule and the same machine for - weeks and I haven't touched the automation. Can you investigate why? + My nightly CustomerHubSync job from folder Shared faulted on its most + recent scheduled run, on the Use Browser step. It has run on the same + schedule and the same machine for weeks and I haven't touched the + automation. Can you investigate why? success_criteria: - type: skill_triggered diff --git a/tests/tasks/uipath-troubleshoot/activity-packages/uia-click-noop-simulate-tech/task.yaml b/tests/tasks/uipath-troubleshoot/activity-packages/uia-click-noop-simulate-tech/task.yaml index ad2c40c655..fef5825c4e 100644 --- a/tests/tasks/uipath-troubleshoot/activity-packages/uia-click-noop-simulate-tech/task.yaml +++ b/tests/tasks/uipath-troubleshoot/activity-packages/uia-click-noop-simulate-tech/task.yaml @@ -42,9 +42,10 @@ reference: file: RESOLUTION.md initial_prompt: | - My ClaimsSubmit job in folder Finance finished Successful last night, but it - never clicked the Submit button in our Java claims app — the claim stayed in - Draft. There was no error at all. Why did it silently do nothing? + My ClaimsSubmit job in folder Finance finished Successful on its most + recent run, but it never clicked the Submit button in our Java claims app — + the claim stayed in Draft. There was no error at all. Why did it silently + do nothing? success_criteria: - type: skill_triggered diff --git a/tests/tasks/uipath-troubleshoot/products/integration-service/rpa-is-connection-not-authorized-cns/task.yaml b/tests/tasks/uipath-troubleshoot/products/integration-service/rpa-is-connection-not-authorized-cns/task.yaml index d8832ef40b..c65e169cf2 100644 --- a/tests/tasks/uipath-troubleshoot/products/integration-service/rpa-is-connection-not-authorized-cns/task.yaml +++ b/tests/tasks/uipath-troubleshoot/products/integration-service/rpa-is-connection-not-authorized-cns/task.yaml @@ -36,7 +36,7 @@ reference: file: RESOLUTION.md initial_prompt: | - The LeadImport job in our CRM folder started failing this morning on every run. It ran fine for weeks and nobody changed the workflow. Can you troubleshoot? + The LeadImport job in our CRM folder started failing on every run. It ran fine for weeks and nobody changed the workflow. Can you troubleshoot? success_criteria: - type: skill_triggered diff --git a/tests/tasks/uipath-troubleshoot/products/orchestrator/credential-store-unavailable/task.yaml b/tests/tasks/uipath-troubleshoot/products/orchestrator/credential-store-unavailable/task.yaml index 909a810555..22047bfecd 100644 --- a/tests/tasks/uipath-troubleshoot/products/orchestrator/credential-store-unavailable/task.yaml +++ b/tests/tasks/uipath-troubleshoot/products/orchestrator/credential-store-unavailable/task.yaml @@ -49,7 +49,7 @@ reference: initial_prompt: | My SecurePortalBot jobs in the SecureOps folder started failing at - launch this morning — a teammate says one of their bots in the same + launch — a teammate says one of their bots in the same folder is failing the same way too. Can you find out why they won't start? success_criteria: diff --git a/tests/tasks/uipath-troubleshoot/products/orchestrator/logon-failure-password-mismatch/RESOLUTION.md b/tests/tasks/uipath-troubleshoot/products/orchestrator/logon-failure-password-mismatch/RESOLUTION.md index 50619453cd..6c26a1a5d7 100644 --- a/tests/tasks/uipath-troubleshoot/products/orchestrator/logon-failure-password-mismatch/RESOLUTION.md +++ b/tests/tasks/uipath-troubleshoot/products/orchestrator/logon-failure-password-mismatch/RESOLUTION.md @@ -26,7 +26,7 @@ network, and RDP path are healthy. The fault is scoped to the `UIPATH\USER1` credential. **Why:** AD `PasswordLastSet` for `UIPATH\USER1` is -`2026-05-11T07:14:00Z` (yesterday, per the initial report and the +`2026-05-11T07:14:00Z` (per the initial report and the `_meta.ad_password_last_set_observed` annotation on `or users get`). The Orchestrator-stored credential record shows `PasswordLastSet: 2026-05-04T09:00:00Z` — seven days older than AD. diff --git a/tests/tasks/uipath-troubleshoot/products/orchestrator/logon-failure-password-mismatch/task.yaml b/tests/tasks/uipath-troubleshoot/products/orchestrator/logon-failure-password-mismatch/task.yaml index 7b58e1badc..ae89e8ed63 100644 --- a/tests/tasks/uipath-troubleshoot/products/orchestrator/logon-failure-password-mismatch/task.yaml +++ b/tests/tasks/uipath-troubleshoot/products/orchestrator/logon-failure-password-mismatch/task.yaml @@ -50,10 +50,10 @@ reference: initial_prompt: | My InvoiceIngestor process has been faulting in Orchestrator - every time it runs since this morning — each job dies within a + every time it runs — each job dies within a second of starting. One thing that might be relevant: my AD admin rotated - the password for the UIPATH\USER1 service account yesterday - (2026-05-11). Can you investigate? + the password for the UIPATH\USER1 service account on + 2026-05-11. Can you investigate? success_criteria: - type: skill_triggered @@ -91,7 +91,7 @@ simulation: its investigation and trust its expertise. You only have the information you wrote in your initial report — no extra data. The only AD fact you know is that an AD admin rotated the - password for UIPATH\USER1 yesterday (2026-05-11). You do not + password for UIPATH\USER1 on 2026-05-11. You do not know the new password, you do not have AD console access, and you cannot run PowerShell on a domain controller. goal: | @@ -102,7 +102,7 @@ simulation: constraints: - "If the agent asks whether to expand investigation scope (any new product domain such as orchestrator, identity, ad, system-activities, activity-packages, ui-automation), always answer Yes — pick the recommended / first / affirmative option." - "If the agent asks how to proceed when data is missing, tell it to proceed with best-effort findings using the evidence already gathered." - - "If the agent asks for the AD PasswordLastSet timestamp, repeat: the AD admin rotated the password yesterday (2026-05-11) — that is all you know." + - "If the agent asks for the AD PasswordLastSet timestamp, repeat: the AD admin rotated the password on 2026-05-11 — that is all you know." - "If the agent asks whether the account is locked, say you cannot check AD directly — point them at the Robot service logs and Orchestrator data." - "If the agent asks where the failing project's source or code is, tell it the project source is available in the current working directory." - "Never invent or provide new factual data — you don't know any details beyond your initial report, other than the project-source location noted above." diff --git a/tests/tasks/uipath-troubleshoot/products/orchestrator/queue-items-failing-test/task.yaml b/tests/tasks/uipath-troubleshoot/products/orchestrator/queue-items-failing-test/task.yaml index 8af83ca0f3..d08964d6f1 100644 --- a/tests/tasks/uipath-troubleshoot/products/orchestrator/queue-items-failing-test/task.yaml +++ b/tests/tasks/uipath-troubleshoot/products/orchestrator/queue-items-failing-test/task.yaml @@ -39,7 +39,7 @@ reference: file: RESOLUTION.md initial_prompt: | - My ItemsQueue has 4 failed items today, please investigate. + My ItemsQueue has 4 failed items, please investigate. success_criteria: - type: skill_triggered diff --git a/tests/tasks/uipath-troubleshoot/products/orchestrator/rpa-consecutive-system-exceptions/task.yaml b/tests/tasks/uipath-troubleshoot/products/orchestrator/rpa-consecutive-system-exceptions/task.yaml index 2e77e7997d..86a6a3a58a 100644 --- a/tests/tasks/uipath-troubleshoot/products/orchestrator/rpa-consecutive-system-exceptions/task.yaml +++ b/tests/tasks/uipath-troubleshoot/products/orchestrator/rpa-consecutive-system-exceptions/task.yaml @@ -47,7 +47,7 @@ reference: initial_prompt: | My OrderReconciliation process in the OpsAutomation folder aborted - this morning with a "maximum number of consecutive system + with a "maximum number of consecutive system exceptions was reached" error. What actually caused it and how do I stop it happening again? diff --git a/tests/tasks/uipath-troubleshoot/products/orchestrator/rpa-executor-service-disconnect/task.yaml b/tests/tasks/uipath-troubleshoot/products/orchestrator/rpa-executor-service-disconnect/task.yaml index da33e03f24..6ac55fcad5 100644 --- a/tests/tasks/uipath-troubleshoot/products/orchestrator/rpa-executor-service-disconnect/task.yaml +++ b/tests/tasks/uipath-troubleshoot/products/orchestrator/rpa-executor-service-disconnect/task.yaml @@ -36,7 +36,7 @@ reference: file: RESOLUTION.md initial_prompt: | - My NightlyPost process in the Batch Ops folder faulted on last night's + My NightlyPost process in the Batch Ops folder faulted on its most recent scheduled run on BATCH-BOT-02 — it had been running for about a minute and then died. The previous nights ran fine on the same machine. Why did this run fail and what should I do? diff --git a/tests/tasks/uipath-troubleshoot/products/orchestrator/rpa-serverless-robot-units/task.yaml b/tests/tasks/uipath-troubleshoot/products/orchestrator/rpa-serverless-robot-units/task.yaml index e986db9c84..355e41e61e 100644 --- a/tests/tasks/uipath-troubleshoot/products/orchestrator/rpa-serverless-robot-units/task.yaml +++ b/tests/tasks/uipath-troubleshoot/products/orchestrator/rpa-serverless-robot-units/task.yaml @@ -38,7 +38,7 @@ reference: initial_prompt: | My InvoiceParse automation in the Cloud Robots folder won't start anymore — it goes straight to Faulted without ever running. It runs as a serverless - cloud robot. This started today and now every run fails. Why, and how do I + cloud robot. This started recently and now every run fails. Why, and how do I fix it? success_criteria: