- 概要
- はじめに
- 概念
- UiPath CLI を使用する
- 使用ガイド
- CI/CD レシピ
- コマンド リファレンス
- 概要
- 終了コード
- グローバル オプション
- 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
- テスト データのキューを追加
- 追加-テスト-データ-バリエーション
- 分析
- 開発
- プロジェクトを作成
- 差分
- アクティビティを検索
- GET-ANALYZER-RULES
- get-default-activity-xaml
- エラーを取得
- 手動テスト用のテスト ケースを取得
- 手動テストステップを取得
- get-library-object-repository
- get-object-repository
- get-versions
- Get-workflow-example
- indicate-application
- 要素を示す
- inspect-package
- install-data-fabric-entities
- パッケージのインストールまたは更新
- list-data-fabric-entities
- list-instances
- list-workflow-examples
- パッケージ化
- パブリッシュ
- remote
- 元に戻す
- run, debug & execution
- ファイル名を実行
- 検索テンプレート
- スタートスタジオ
- 実行を停止
- tm
- UIA
- uip tasks
- uip traces
- uip traces feedback
- 移行
- 参照とサポート
Syntax and options for `uip maestro flow debug-instance`, a low-level debugger control surface for stepping through, inspecting, and steering a Studio Web debug session.
uip maestro flow debug-instance is a low-level debugger control surface — create a debug instance, then step through it, inspect its variables and incidents, and cancel or continue it. This is a different, more granular layer than uip maestro flow debug, which uploads a project and polls to completion in one call. debug-instance is what you'd reach for to build a custom debugging tool (for example, an editor integration) around Studio Web's debug protocol, driving one step at a time.
概要
uip maestro flow debug-instance create --solution-id <id> --project-id <id> --entry-point <path> [--process-type <type>] [--debug-mode <mode>] [--simulation-mode <mode>] [-i, --inputs <json>]
uip maestro flow debug-instance status <instance-id>
uip maestro flow debug-instance breakpoints <instance-id> [--inputs <json|@file>]
uip maestro flow debug-instance cancel <instance-id>
uip maestro flow debug-instance continue <instance-id> [--inputs <json|@file>]
uip maestro flow debug-instance incidents <instance-id>
uip maestro flow debug-instance variables <instance-id> [--parent-element-id <id>]
uip maestro flow debug-instance variables-set <instance-id> [--inputs <json|@file>]
uip maestro flow debug-instance variables-all <instance-id>
uip maestro flow debug-instance create --solution-id <id> --project-id <id> --entry-point <path> [--process-type <type>] [--debug-mode <mode>] [--simulation-mode <mode>] [-i, --inputs <json>]
uip maestro flow debug-instance status <instance-id>
uip maestro flow debug-instance breakpoints <instance-id> [--inputs <json|@file>]
uip maestro flow debug-instance cancel <instance-id>
uip maestro flow debug-instance continue <instance-id> [--inputs <json|@file>]
uip maestro flow debug-instance incidents <instance-id>
uip maestro flow debug-instance variables <instance-id> [--parent-element-id <id>]
uip maestro flow debug-instance variables-set <instance-id> [--inputs <json|@file>]
uip maestro flow debug-instance variables-all <instance-id>
Honors global options. Exit codes follow the standard contract. Requires uip login.
uip maestro flow debug-instance create
Begin a debug session in Orchestrator and create the corresponding debug instance for an already-uploaded solution.
オプション
| オプション | Required | 既定 (Default) | 説明 |
|---|---|---|---|
--solution-id <id> | ○ | — | Solution ID from a previous upload or Studio Web. |
--project-id <id> | ○ | — | Studio Web project ID within the solution. |
--entry-point <path> | ○ | — | Entry point path, e.g. /Main.bpmn#start. |
--process-type <type> | × | processOrchestration | Process type. |
--debug-mode <mode> | × | Default | Default (pause at breakpoints), StepByStep (pause at every step), or SingleStep (execute exactly one step). |
--simulation-mode <mode> | × | None | None, All (simulate every element), or Selective (simulate except opt-outs). |
-i, --inputs <json> | × | {} | 引数を JSON 文字列として入力します。 |
Invalid --debug-mode/--simulation-mode values fail fast, listing the valid set.
データシェイプ
{
"Code": "DebugInstanceCreated",
"Data": {
"instanceId": "…",
"runId": "…",
"jobKey": "b2c3d4e5-…"
},
"Instructions": "Use 'debug-instance status <instance-id>' to check the run. Use 'debug-instance incidents <instance-id>' or 'debug-instance variables <instance-id>' to inspect it."
}
{
"Code": "DebugInstanceCreated",
"Data": {
"instanceId": "…",
"runId": "…",
"jobKey": "b2c3d4e5-…"
},
"Instructions": "Use 'debug-instance status <instance-id>' to check the run. Use 'debug-instance incidents <instance-id>' or 'debug-instance variables <instance-id>' to inspect it."
}
uip maestro flow debug-instance status
Get per-element execution status. Argument: <instance-id>. Data shape: Code: "DebugInstanceStatus".
uip maestro flow debug-instance breakpoints
Update the breakpoint set for a paused instance. Argument: <instance-id>. Option: --inputs <value> — breakpoints payload as a JSON string, an @file path, or piped via stdin. Data shape: Code: "DebugInstanceBreakpointsUpdated".
uip maestro flow debug-instance cancel
Cancel a debug instance. Argument: <instance-id>. Data shape: Code: "DebugInstanceCanceled".
uip maestro flow debug-instance continue
Resume execution on a paused instance. Argument: <instance-id>. Option: --inputs <value> — a JSON string, @file path, or stdin; defaults to {"nextStep": false} when omitted (run to the next breakpoint rather than a single step). Data shape: Code: "DebugInstanceContinued".
uip maestro flow debug-instance incidents
Get incidents raised during the debug session. Argument: <instance-id>. Data shape: Code: "DebugInstanceIncidents", Data is an array (empty if none).
uip maestro flow debug-instance variables
Get variables for the instance. Argument: <instance-id>. Option: --parent-element-id <id> — filter to variables scoped under one element. Data shape: Code: "DebugInstanceVariables".
uip maestro flow debug-instance variables-set
Patch (partially update) variables. Argument: <instance-id>. Option: --inputs <value> — patch payload as JSON string, @file path, or stdin. Data shape: Code: "DebugInstanceVariablesSet".
uip maestro flow debug-instance variables-all
Get all variables, including subprocess scopes. Argument: <instance-id>. Data shape: Code: "DebugInstanceVariablesAll".
参照
uip maestro flow debug— the higher-level, upload-and-poll debug command most workflows should use insteaduip maestro flow instance— the equivalent control surface for a published, running instance rather than a debug session- フローの概要
- グローバル オプション、 終了コード
- 概要
- uip maestro flow debug-instance create
- オプション
- データシェイプ
- uip maestro flow debug-instance status
- uip maestro flow debug-instance breakpoints
- uip maestro flow debug-instance cancel
- uip maestro flow debug-instance continue
- uip maestro flow debug-instance incidents
- uip maestro flow debug-instance variables
- uip maestro flow debug-instance variables-set
- uip maestro flow debug-instance variables-all
- 参照