Which is NOT a step to build an orchestration?

Building an orchestration involves defining the sequence of tasks and processes that need to be executed. Each of the components required for orchestration contributes to creating a well-structured and effective automation path.

Adding stages is essential as it helps in identifying the various phases of the orchestration where specific actions can be executed. Interactive steps allow users to include engagement points where input or decisions are made, enhancing the flexibility of the process. Logic elements are crucial for introducing conditions and branching paths within the orchestration, enabling more sophisticated decision making.

While documentation is a vital part of any development process, it is not a technical step within the orchestration build itself. Although having documentation is beneficial for clarity and future reference, it does not contribute to the execution or functionality of the orchestration directly. Thus, it stands out as not being a step to build an orchestration.