Nothing here yet.
That’s a really good point. Retries are only truly safe when each step knows exactly what input it worked on and what output it produced. Versioning those outputs also makes conflicts visible instead of letting a retry overwrite newer data. Definitely something worth considering for production workflows.
Absolutely agree. The memory/scale point is something I should have emphasized more a long-running request can become a real problem once multiple requests are running at the same time. Idempotency and queue limits are also great points, especially for workflows that can trigger side effects. And separating queue time from execution time in metrics makes a lot of sense for knowing where the actual bottleneck is. Thanks for adding these points!
