- Vue d'ensemble (Overview)
- Démarrer
- Concepts
- Utilisation de la UiPath CLI
- Guides pratiques
- Revenus CI/CD
- Référence de commande
- Vue d'ensemble (Overview)
- Codes de sortie
- Options globales
- agent codé uip
- encodeur UIP
- uip ancrage dans le contexte
- UiPath Docsai
- Fonction UiP
- garde-fous UiP
- configuration llm uip
- uip llm-passerelle
- uip maestro authoring
- uip maestro registry
- uip model-hub
- Tâches (Jobs)
- Dossiers
- Processus
- process-roi
- Paquets
- Machines
- Utilisateurs
- Rôles
- Licences
- Flux
- Pièces jointes (Attachments)
- Sessions
- Calendriers
- magasins d'informations d’identification
- journaux-audit
- paramètres
- Actifs
- Compartiments
- Compartiment-fichiers
- Bibliothèques
- Files d'attente (Queues)
- queue-roi
- éléments de la file d'attente
- Déclencheurs (Triggers)
- Webhooks
- activities find
- activities get-default-xaml
- Analyser
- analyzer-rules list
- Construire
- Nettoyage
- data-fabric-entities install
- data-fabric-entities list
- files diff
- Get-Library-Object-Repository
- Récupérer le référentiel d'objets
- Init
- instances list
- Créer un package
- packages inspect
- packages install
- packages versions
- Publier
- Distant
- restore
- exécuter, déboguer et amp; Exécution
- paramètres
- studio start
- templates search
- test-data add-entity
- test-data add-queue
- test-data add-variation
- TM
- UIA
- Valider
- workflow-examples get
- workflow-examples list
- tâches UIP
- pièce jointe
- Champ personnalisé
- defects
- Exécutions
- export-jobs
- migration
- Libellé Objet
- Créer un package
- scénarios-perf
- groupes-de-charge-scénarios-perf
- données d’exécution de perf-scenario
- rapport de scénarios de performances
- Projet
- project-permissions
- prompts
- Rapport
- Prérequis
- Résultat
- Exécuter
- schedules
- testcaselog
- Cas de test
- Ensembles de tests
- Journal des étapes de test
- Utilisateur (User)
- Attendre
- Traçages UIP
- Commentaires sur les traces UIP
- Migration
- Référence et assistance
uip codedapp validate
Syntax and options for `uip codedapp validate`, which checks whether a coded app path name is free and which app holds it.
uip codedapp validate checks whether a coded app path name (https://<org>.uipath.host/<path-name>) is free in the organization, and names the app that holds it when it is taken. Run it before uip codedapp deploy --path-name to avoid a path-name conflict.
The path name is converted the same way deploy converts --path-name (refer to Package ID), so both commands act on the same name. A value that is empty after conversion, or longer than 64 characters, is rejected before any request is sent.
The check is organization-scoped, so the command takes no tenant or folder options.
Synthèse
uip codedapp validate --path-name <name> [options]
uip codedapp validate --path-name <name> [options]
Options
| Drapeau | Description |
|---|---|
--path-name <name> | Required. App path name to check. Must contain at least one letter or digit. |
--base-url <url> | URL de base UiPath (remplacer l'authentification). |
--org-id <id> | ID de l’organisation (remplissage d’authentification). |
--org-name <name> | Nom de l'organisation (remplissage d'authentification). |
--access-token <token> | Jeton d’accès (remplacer l’authentification). |
Exemple
uip codedapp validate --path-name my-app
uip codedapp validate --path-name my-app
Format des données (--sortie json)
A free path name:
{
"Code": "CodedAppPathNameChecked",
"Data": {
"PathName": "my-app",
"Available": true,
"OccupiedBy": null
}
}
{
"Code": "CodedAppPathNameChecked",
"Data": {
"PathName": "my-app",
"Available": true,
"OccupiedBy": null
}
}
A taken path name also describes the app that holds it:
{
"Code": "CodedAppPathNameChecked",
"Data": {
"PathName": "my-app",
"Available": false,
"OccupiedBy": {
"Id": "6f1c2b4a-0000-0000-0000-000000000001",
"DeploymentTitle": "My App",
"Title": "My App package title",
"SystemName": "my-app_abc123",
"SemVersion": "1.2.0",
"DeployVersion": 3,
"DeploymentDescription": "Expense approvals",
"IsLatestVersion": true,
"IsAppPublic": false,
"DateDeployed": "2026-09-18T10:12:04.000Z",
"DeploymentFolder": {
"Key": "3f8b1d22-0000-0000-0000-000000000001",
"DisplayName": "Shared"
},
"IsResourceActivated": true,
"RoutingName": "my-app"
}
}
}
{
"Code": "CodedAppPathNameChecked",
"Data": {
"PathName": "my-app",
"Available": false,
"OccupiedBy": {
"Id": "6f1c2b4a-0000-0000-0000-000000000001",
"DeploymentTitle": "My App",
"Title": "My App package title",
"SystemName": "my-app_abc123",
"SemVersion": "1.2.0",
"DeployVersion": 3,
"DeploymentDescription": "Expense approvals",
"IsLatestVersion": true,
"IsAppPublic": false,
"DateDeployed": "2026-09-18T10:12:04.000Z",
"DeploymentFolder": {
"Key": "3f8b1d22-0000-0000-0000-000000000001",
"DisplayName": "Shared"
},
"IsResourceActivated": true,
"RoutingName": "my-app"
}
}
}
Both outcomes are a success and exit 0, so scripts read Data.Available rather than the exit code. When a path name is taken but the holding app cannot be determined, OccupiedBy is null and the CLI prints a warning on stderr.
Modes d’échec
ErrorCode | Origine |
|---|---|
permission_denied | The account lacks Apps or Apps.Read on the organization. For an external application token without an Apps scope, the message names the Apps.Read scope to grant and add to uip login --scope. |
authentication_required | The session is invalid or expired. Run uip login. |
server_error | The service could not answer. The name is neither confirmed free nor confirmed taken; retry later. |
Associé
- uip codedapp deploy: deploy an app under the path name you checked.