Why is it recommended to design and debug orchestrations in a sandbox prior to deploying in production?

Designing and debugging orchestrations in a sandbox prior to deploying them in a production environment is crucial to ensure no record changes are rolled back on failure. When testing in a sandbox, you can thoroughly assess the orchestration process without the risk of altering real production data. This means any mistakes or failures during the debugging process do not impact the live system or its data integrity.

When orchestrations are executed, they can make various changes to records. If an orchestration fails in production, it could potentially lead to incomplete operations or data inconsistencies. By testing in a sandbox, you can simulate these orchestration processes and fully understand how they behave, ensuring that when they are deployed in production, they operate correctly and any failure during execution does not result in unwanted rollbacks that could affect users or data negatively.

This practice ultimately leads to a more reliable and stable production environment, designed to handle any issues that may arise without the potential for critical data loss or corruption.