Documentation

​
​

Development

User Acquisition

Monetization

Industry

Unity Version Control

DevOps

On-prem

Gluon

Editor plug-in

Open Unity Dashboard

Unity Version Control

​
​
Unity Version Control
  • Overview
  • Cloud Repositories organization update
  • Installation
  • Use UVCS with the Unity Editor
  • Unity Version Control plugins
  • Concepts
    • Organizations
    • Repositories
    • Workflows and partial replicas
    • Security
    • Dynamic workspaces (Windows)
    • File explorer
    • Code reviews
    • Branches
    • Merge conflicts
    • Mergebots
    • Xlinks
    • Smart Locks
    • Symlink Support
    • Triggers
      • Types of trigger
      • List of available triggers
      • Detailed trigger reference
      • Input communication
      • Output communication
      • Common environment variables
      • server.conf variables
      • Client side variables
      • Filters
      • Web triggers
  • Tutorials
  • On-Prem
  • Gluon
  • CLI and shortcut references
  • Release Notes
  1. Unity Version Control (previously Plastic SCM)

Output

Understand output variables for triggers in Unity Version Control.
Read time 1 minute
Last updated 10 months ago
The trigger script uses the result code to communicate the result of its execution. UVCS interprets these result codes as one of the following:
  • Zero (0): Trigger finished correctly. Operation can continue.
  • Non-zero (>0): Trigger failed. Operation cannot continue.
When a trigger fails, UVCS sends the standard output of the trigger to the client as an error message:
  • If the result is non-zero for a 
    before
    trigger, the operation cancels, and the client displays the error.
  • If the result is non-zero for an 
    after
    trigger, the operation has been already performed and can't undo. The client displays the exception.
When a server-side trigger fails because the executable is missing, the server treats it as a non-zero exit code.
However, starting on UVCS (previously Plastic SCM) version 8.0.16.3388, when a client-side trigger fails because the executable is missing, the client treats it as a zero exit code.
The error registers as a zero exit code in case you want to distribute your client-side triggers through your repository.
Note
If triggers such as 
before-mkworkspace
, 
after-mkworkspace
, 
before-setselector
, 
after-setselector
, and 
before-update
fail with a non-zero exit code because the trigger executable isn't downloaded to your workspace, you need to remove the trigger configuration, run the operation, and configure the trigger again.
Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.

    Report a problem with this page