@uipath/skills 1.201.0-preview.621 → 1.202.0-preview.635

package/skills/uipath-process-mining/references/lifecycle-and-rbac.md

@@ -16,12 +16,14 @@ query commands (default `dev`):
 Typical loop: develop and validate on `--stage dev` with a subset → publish → let
 consumers read the **dashboards** on the published data.
 
-> **CLI caveat:** `uip pm query --stage published` is currently **not reachable** —
-> `/query/{id}/published` needs a completed ingestion on that stage and no `uip pm`
-> path produces one (`apps publish` answers `IngestionNeeded: true`, but a following
-> `ingestions create --wait` still leaves published querying at
-> `UserError_InvalidOrNoIngestion`; verified against a live tenant). So publishing
-> promotes the app to the **dashboards**, but **CLI-driven `query` stays on `dev`**.
+> **Querying `published`:** `/query/{id}/published` needs a **completed ingestion on
+> that stage**. `apps publish` promotes the definition and answers
+> `IngestionNeeded: true`; materialize the rows with
+> **`uip pm ingestions create <app> --stage published --wait`** — `ingestions create`
+> takes `--stage` (the stage to ingest into) — after which `query --stage published`
+> works. Before that ingestion completes it 400s `UserError_InvalidOrNoIngestion`.
+> Querying published is **optional**: `dev` stays the fast iteration loop, and
+> consumers read the **dashboards** either way.
 
 ## Publishing
 
@@ -40,8 +42,8 @@ clobbering a newer model. The result envelope carries:
   after a re-ingest; publishing alone promotes the definition, not the rows.
 
 So the full promote loop is: validate on `dev` → `uip pm apps publish <app>` →
-`uip pm ingestions create <app> --wait` when `IngestionNeeded` → analyse on
-`--stage published`.
+`uip pm ingestions create <app> --stage published --wait` when `IngestionNeeded`
+→ optionally analyse on `--stage published` (the dashboards read it either way).
 
 ## RBAC — configured at the platform layer, not in `uip pm`
 

package/skills/uipath-process-mining/references/model-editing.md

@@ -82,7 +82,7 @@ the footgun below), so `fields set` is the *safe* way to change a kind. Caveat:
 comparisons in the typed model `data` (calculated fields, metrics); a kind change that conflicts only
 with an opaque dashboard **view** filter/chart is not caught, so publish and re-open to confirm.
 
-## The data-kind footgun (DNA-46960)
+## The data-kind footgun
 
 A customer's app failed to open with exactly the error above. Root cause, from their exported app:
 a metric **`% Tijdigheid`** was `PERCENTAGE( DOORLOOPTIJD[duration] lt 864000000[numeric] )` — a

package/skills/uipath-process-mining/references/querying.md

@@ -3,9 +3,10 @@
 Pull numbers out of a built app. Subcommands: `info` (metadata), `run`
 (aggregate group-by + metrics), `details` (raw rows), `percentile`, `rca`
 (root-cause), `insights` (process insights), `layout`. All take `--stage
-dev|published` (default `dev`) — but query on **`dev`**: `--stage published` is
-currently unreachable via the CLI (`UserError_InvalidOrNoIngestion`; no `uip pm`
-path completes a published-stage ingestion — see
+dev|published` (default `dev`). Iterate on **`dev`**; `--stage published` needs a
+completed ingestion **on that stage** — run
+`ingestions create <app> --stage published --wait` after `apps publish`. Until that
+ingestion completes the query 400s `UserError_InvalidOrNoIngestion` (see
 [`lifecycle-and-rbac.md`](lifecycle-and-rbac.md)).
 
 ## Start with `query info`