[Docs] Docs on how Propeller ensures a task is executed exactly once

[sonjaer]

Description

I was curious how Propeller ensures a task is executed exactly once? I was curious since we have non idempotent tasks that we wouldn't want to run twice.
Is there any instance when this could not be true? When deploying a new Propeller or error writing to etcd?
Is this something that could be added to the Propeller Architecture docs here

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[github-actions]

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

[github-actions]

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏

[eapolinario]

Calling Flyte's model exactly once is not correct. Flyte does in fact a lot of heavy lifting to ensure that resources are not wasted and for a given execution inputs and outputs are never overwritten.