Can one database transaction roll back an entire agent workflow?
Only operations participating in that transaction can roll back together. Model calls, payments, email and other external effects need explicit idempotency and recovery contracts.
Answered in
Modular Monoliths for Agent Workflows: Where Local Calls HelpAgent workflows amplify needless service hops. Modular boundaries and short transactions simplify execution; remote effects still need durable recovery.
Read the full analysisOther questions this article answers
More development best practices questions
- How much faster does AI help developers write code?
- What is code churn and how has AI impacted it?
- Why did developer PR throughput increase by only 7.76% despite a 65% increase in AI tool usage?
- What are the security risks associated with AI-generated code?
- How does AI impact the Total Cost of Ownership (TCO) of software?
- Does a larger context window prevent agent loops?
- Should every failed test trigger git reset --hard?
- Do agent applications require a modular monolith?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.