What happens when an orchestration fails?

When an orchestration fails, the correct understanding is that no automatic rollback occurs. This means that any changes that were made up to the point of failure will remain intact and not be undone. Organizations often need to handle error scenarios intentionally, which may involve reviewing logs or implementing a manual rollback process if necessary. This is particularly relevant in complex workflows where maintaining certain data states is essential to ensure data integrity and continuity of operations.

In contrast, the other options suggest various forms of automatic recovery or rollback mechanisms, which do not apply in this scenario. Automatic rollbacks can introduce complexity and potential issues if not handled correctly; thus, Salesforce does not automatically revert changes in the event of an orchestration failure to allow for better control and decision-making by the user or administrator. The lack of automatic rollback empowers teams to investigate issues without inadvertently erasing valid data changes.