Hi all! Is there a documented reason as to why checkpointing is disabled by default on local Prefect flows? That is, why is the behavior opt-in when other frameworks typically have it as a requirement (or opt-out)? https://docs.prefect.io/core/concepts/results.html#pipeline-persisted-results

Hi Danny! I'm not sure if it's explicitly documented, but local flows are essentially treated as testing environments and are thus stateless. All statefulness is delegated to Server / Cloud. When running an orchestrated flow (e.g., with Server or Cloud) checkpointing actually is the default behavior as you expect

Ah! Understood. Thanks for clarifying @Chris White!

👍 👍 anytime!