uip solution upload

uip solution upload uploads a local solution to UiPath Studio Web for browser-based editing. It bundles the solution into an internal .uis archive, sends it to Studio Web, and (on success) prints a URL you can open directly in the designer.

Unlike uip solution pack + uip solution publish, which produce a deployable .zip for Orchestrator, upload targets the interactive Studio Web authoring surface. Use this when you want to continue editing a solution collaboratively in the browser.

If the solution already exists on Studio Web (matched by the SolutionId inside its .uipx), upload overwrites the existing copy; otherwise it is imported as a new solution and the returned ID is written back into the local .uipx so subsequent uploads update in place.

Synopsis

uip solution upload <solutionPath> [--login-validity <minutes>]

The command honours the global options and returns the standard exit codes.

Arguments

• <solutionPath> (required) — One of:
  • A solution directory containing a .uipx manifest (most common).
  • A .uipx file (the command resolves the directory containing it).
  • A .uis file (a pre-bundled solution archive; uploaded as-is for backward compatibility).

Options

• --login-validity <minutes> — Minimum minutes before token expiration to trigger a refresh. Defaults to 10.

Exemples

Minimal

uip solution upload ./my-solution

Upload a specific .uipx

uip solution upload ./workspace/my-solution/my-solution.uipx

Scripting — open the returned designer URL

URL=$(uip solution upload ./my-solution --output-filter "Data.DesignerUrl" --output plain)
open "$URL"   # macOS

Data shape (--output json)

{
  "Code": "SolutionUpload",
  "Data": {
    "Status": "Uploaded successfully",
    "SolutionId": "a1b2c3d4-0000-0000-0000-000000000001",
    "DesignerUrl": "https://cloud.uipath.com/myorg/mytenant/studio_/designer/p1?solutionId=a1b2c3d4-0000-0000-0000-000000000001",
    "Response": { }
  }
}

• SolutionId — the identity Studio Web assigned (on first upload) or matched (on overwrite). Also written back into the local .uipx so the next upload updates the same solution.
• DesignerUrl — ready-to-open URL for the first project in the solution, pre-scoped to the solution. null when Studio Web does not return a project ID.
• Response — raw Studio Web response payload. Useful for debugging; not part of a stable contract.

Side effects

• Bindings sync. Before uploading, upload re-scans each project's bindings_v2.json and reconciles the solution's resource declarations, equivalent to running uip solution resource refresh.
• Connection overwrites. After upload, any connection overwrites detected in the solution's resources/solution_folder/connection/ directory are patched onto Studio Web against the authenticated user's Personal Workspace folder. Failures here are logged as warnings and do not fail the command.
• SolutionId write-back. On a fresh upload, the returned solution ID replaces (or populates) the SolutionId field in the local .uipx.

Related commands

• uip solution pack + uip solution publish — deployment pipeline alternative to upload.
• uip solution delete — remove a Studio Web solution by its SolutionId.
• uip solution new — scaffold a solution before uploading.

Voir également

• Authentication — upload requires an active session.
• uip solution overview.