- Overview
- Get started
- Concepts
- Using UiPath CLI
- How-to guides
- CI/CD recipes
- Command reference
- Overview
- Exit codes
- Global options
- uip codedagent
- uip coder
- uip context-grounding
- uip docsai
- uip function
- uip guardrails
- uip llm-configuration
- uip llm-gateway
- uip maestro authoring
- uip maestro registry
- uip model-hub
- activities find
- activities get-default-xaml
- analyze
- analyzer-rules list
- build
- cleanup
- data-fabric-entities install
- data-fabric-entities list
- files diff
- get-library-object-repository
- get-object-repository
- init
- instances list
- pack
- packages inspect
- packages install
- packages versions
- publish
- remote
- restore
- run, debug & execution
- settings
- studio start
- templates search
- test-data add-entity
- test-data add-queue
- test-data add-variation
- tm
- uia
- validate
- workflow-examples get
- workflow-examples list
- uip tasks
- uip traces
- uip traces feedback
- Migration
- Reference & support
uip insights filter-folders
Syntax and options for `uip insights filter-folders`, which discovers folders with recent Insights activity for use with --folder-key filters.
uip insights filter-folders discovers folders that have had Insights activity recently, restricted to folders the current caller can access. Use it to find the --folder-key values that jobs and other Insights filters accept.
"Recent" is a fixed 30-day window set by the backend — it cannot be changed with a flag. This route is also feature-gated to Cloud and Dedicated SaaS deployments; on other deployment types the command fails with a ConfigError rather than an empty result.
Synopsis
uip insights filter-folders list [-l <n>] [-o <n>]
uip insights filter-folders list [-l <n>] [-o <n>]
This verb honors the global options and the standard exit codes. It does not accept -t, --tenant — it uses the tenant selected during uip login.
uip insights filter-folders list
List folders with Insights activity in the backend's fixed 30-day window.
Options
| Flag | Description |
|---|---|
-l, --limit <number> | Maximum rows to return. Defaults to 50. |
-o, --offset <number> | Rows to skip before returning results. |
Rows are deduplicated and sorted after fetching — the backend returns one entry per underlying activity record, not one per distinct folder, so pagination is over the distinct set, not raw activity records. Pagination itself is client-side, over the full unpaginated backend response.
Example
uip insights filter-folders list
uip insights filter-folders list
Data shape
{
"Code": "InsightsFilterFoldersList",
"Data": [
{
"folderName": "Finance/Invoicing",
"folderKey": "f0f0f0f0-0000-0000-0000-000000000001"
}
],
"Pagination": { "Returned": 1, "Limit": 50, "Offset": 0, "Total": 1, "HasMore": false }
}
{
"Code": "InsightsFilterFoldersList",
"Data": [
{
"folderName": "Finance/Invoicing",
"folderKey": "f0f0f0f0-0000-0000-0000-000000000001"
}
],
"Pagination": { "Returned": 1, "Limit": 50, "Offset": 0, "Total": 1, "HasMore": false }
}
folderName carries the full folder path, matching the Insights UI's folder picker. An empty Data array means no matching activity in the 30-day window for the current caller — it is not proof the folder doesn't exist.
Related
- jobs — accepts
--folder-keyvalues discovered here. - filter-processes, filter-machines, filter-queues — sibling discovery commands.