A rollback should stop a commerce agent from doing damage without leaving its failure notifications circulating through processors the team can no longer account for. Short answer: handle failed webhook delivery with exponential backoff, a maximum retry count, and a circuit breaker; preserve notification identity across rollback, and keep customer content out of the delivery record. The retry policy and the data policy must travel together.
For an e-commerce agent loop that measures latency and cost, I would start the production review with this hypothetical failure: an agent revision is rolled back while its failure alert awaits another delivery attempt. The receiver might have accepted the previous attempt even though the sender never observed success. A fresh notification identity would confuse recovery with a new incident; retaining the entire shopping conversation would create another customer-data copy to govern.…