Idempotent Writes, and Why Retries Duplicate Data
Every pipeline gets retried eventually, and a non-idempotent write turns each retry into duplicates. Four patterns that make a write safe to repeat.
8 articles
Every pipeline gets retried eventually, and a non-idempotent write turns each retry into duplicates. Four patterns that make a write safe to repeat.
What a Fabric pipeline rerun actually runs again, why utcNow() and run IDs break recovery, and how to make rerun from failed activity safe.
Decide what an agent does when a tool fails, a step runs out of budget or grounding is weak before launch, and make the release check fail without it.
Typed state and checkpoints don't stop an agent paying twice: five places agent workflow state breaks at its boundaries, and patterns that hold.
Effective incident response minimizes AI system impact and enables quick recovery.
Timeout management in AI applications requires balancing responsiveness with allowing complex operations to complete. Use adaptive timeouts, deadline…
Building reliable agents requires investment in error handling, recovery mechanisms, and observability. These patterns form the foundation for production AI…
Operational resilience is the unsung prerequisite for AI adoption. Practical SRE for AI means instrumenting model performance, bounding cost exposure, and…