The ID (name) to use for the behavior tree. Must always be specified. This is also sometimes called the "process name". The name must be unique within the running solution and should ideally be meaningful to the user.

The behavior tree to create. The name field will be ignored.

The name of the behavior tree to delete.

The name of the behavior tree to retrieve.

The view of the behavior tree to return. Defaults to the FULL view.

The maximum number of behavior trees to return. The service may return fewer than this value. If unspecified, at most 20 behavior trees will be returned. The maximum value is 50; values above 50 will be coerced to 50.

Page token received from a previous call. Provide this to retrieve the subsequent page.

The view of the behavior tree to return. Defaults to the BASIC view.

The behavior trees from the running solution. Behavior trees are returned in alphabetical order (a-z) by name.

A token, which can be sent as page_token to retrieve the next page. If this field is omitted, there are no subsequent pages.

Current state of the solution as a single value. It is recommended not to make assumptions about the sequence of states the solution will transition through as individual states may be skipped. - Starting a solution is safe when state is PLATFORM_READY - Editing the solution is safe when the state is DEPLOYING or READY - Executing processes is only safe when the state is READY

Human-readable reason for the solution being in the current state. Never populated when the state is PLATFORM_READY or READY.

Unique ID of the running solution. Empty if no solution is running or the solution is not deployed from the catalog.

Human readable name of the running solution. Empty if no solution is running.

Whether the solution is running in simulation. The solution is running on real hardware or there is no solution running if this is false.

Name of the cluster.

Version of the platform.

The updated behavior tree. The name field is used to identify the behavior tree to update.

If set to true, a new behavior tree will be created if it does not exist.

The default/unset value. The default depends on the RPC and is documented individually where relevant.

Include basic metadata about the behavior tree (name and tree_id). This is the default view for ListBehaviorTrees.

Include the full contents of the behavior tree.

The state of the solution is not specified. The solution should not be interacted with in this state.

Core platform services are being deployed and are not available yet. It is strongly recommended to wait for the state to transition to either PLATFORM_READY, DEPLOYING or READY before any further action.

All core platform services are ready and no solution is running. It is safe to start a solution in this state.

Solution specific services or assets (e.g. skills, services) are being deployed. The solution can be safely edited while in this state. Executing processes is not recommended until the solution transitions to the READY state.

The solution and all of its services and assets are ready. All functionality, including process execution, is available.

Solution specific services or assets (e.g. skills, services) are being stopped. The solution should not be edited when in this state.

Something went wrong during deployment of the platform or solution. The state_reason field may contain more detailed information.