- 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 model-hub
- add-test-data-entity
- add-test-data-queue
- add-test-data-variation
- analyze
- build
- create-project
- diff
- find-activities
- get-analyzer-rules
- get-default-activity-xaml
- get-errors
- get-manual-test-cases
- get-manual-test-steps
- get-library-object-repository
- get-object-repository
- get-versions
- get-workflow-example
- indicate-application
- indicate-element
- inspect-package
- install-data-fabric-entities
- install-or-update-packages
- list-data-fabric-entities
- list-instances
- list-workflow-examples
- pack
- publish
- remote
- restore
- run, debug & execution
- run-file
- search-templates
- start-studio
- stop-execution
- tm
- uia
- uip tasks
- uip traces
- uip traces feedback
- Migration
- Reference & support
Syntax and options for `uip maestro bpmn refresh`, which regenerates a Maestro project's package metadata files to match its .bpmn file.
uip maestro bpmn refresh updates a project's package metadata files (entry-points.json, bindings_v2.json, operate.json, package-descriptor.json) so they match the current state of the project's .bpmn file. This is the current, non-deprecated replacement for update-metadata. It's registered under the bpmn branch.
Synopsis
uip maestro bpmn refresh <project-path>
uip maestro bpmn refresh <project-path>
Honors global options. Exit codes follow the standard contract.
Arguments
<project-path>(required) — path to the Maestro Process Orchestration project directory (not a single.bpmnfile).
Examples
uip maestro bpmn refresh ./invoice-orchestration
uip maestro bpmn refresh ./invoice-orchestration
Data shape (--output json)
{
"Code": "BpmnRefresh",
"Data": {
"Status": "Updated BPMN package files",
"ProjectPath": "/workspace/invoice-orchestration",
"BpmnFile": "invoice-orchestration.bpmn",
"WrittenFiles": ["entry-points.json", "bindings_v2.json", "operate.json", "package-descriptor.json"],
"UnchangedFiles": []
}
}
{
"Code": "BpmnRefresh",
"Data": {
"Status": "Updated BPMN package files",
"ProjectPath": "/workspace/invoice-orchestration",
"BpmnFile": "invoice-orchestration.bpmn",
"WrittenFiles": ["entry-points.json", "bindings_v2.json", "operate.json", "package-descriptor.json"],
"UnchangedFiles": []
}
}
WrittenFiles lists only the metadata files that actually changed; files already matching the .bpmn file's current state are listed in UnchangedFiles instead.
On failure, the response uses Code: "BpmnRefreshFailed" with Message/Instructions.
See also
uip maestro bpmn update-metadata— deprecated predecessor of this commanduip maestro bpmn validate— structurally validate the.bpmnfile firstuip maestro bpmn pack— pack the project once metadata is current- Maestro overview