Skip to content

Commit

Permalink
Updated playbook action step documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
MaartendeKruijf committed Aug 20, 2024
1 parent af3474c commit 02c5d99
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion docs/content/en/docs/core-components/executer.md
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,7 @@ end
The playbook executor handles execution of playbook action steps. The variables from the top level playbook are injected into the be executed playbook.
It could happen that in the downstream playbook the variables `collide` with the top level playbook. In this case the top level playbook variables are `NOT` transferred to the downstream playbook. `Agents and Targets cannot be transferred` between playbooks at this time. Playbooks are only loaded in the executor and then a new Decomposer is created to execute the playbook.

The result of the step execution will be returned to the decomposer. A result can be either output variables or error status.
The result of the step execution will be returned to the decomposer. A result can be either output variables or error status. Only variables defined in the out_args of the playbook action step will be merged into the global scope of the caller.

```plantuml
package playbookaction{
Expand All @@ -194,6 +194,10 @@ database <- exe
```

NOTE: in the future variables will be merged into the downstream playbook only if they are defined external on the downstream playbook.



### If condition executor
The if-condition executor will process a cacao if-condition step and determine it's output.

Expand Down

0 comments on commit 02c5d99

Please sign in to comment.