What happens when a flow is run in draft mode?

When a flow is run in draft mode, service levels are ignored. This means that the flow operates without actively calculating service levels, allowing developers and testers to focus on testing the process without the influence of service level agreements. This is particularly useful during the development phase when it’s important to understand how the flow functions without the complexity that service levels introduce.

In draft mode, the flow is not treated as a finalized version ready for production. Hence, elements such as service level calculations that could introduce variability or delay in testing are bypassed. This approach emphasizes the testing and refinement of the flow itself over adherence to service level agreements.

Additionally, while it's true that certain behaviors might differ in draft mode, such as bypassing validations or automatic approvals, the key defining feature of draft mode is the disregard for service level calculations, making it easier to assess and troubleshoot the flow's functionality.