---
title: "Comment by Amelia Hernandez on \"Before automating a business workflow, map the exceptions\" | Hashnode"
description: "I like the distinction between a retryable connection problem and a policy question, because they need different next steps. For a lead follow-up workflow, I’d"
url: "https://hashnode.com/posts/before-automating-a-business-workflow-map-the-exceptions/6aed2fb3163419921c314d17/comment/6af4b8dc671d03f826e013bc"
---

[Discussion](https://hashnode.com/posts/before-automating-a-business-workflow-map-the-exceptions/6aed2fb3163419921c314d17)

Comment [Before automating a business workflow, map the exceptions](https://hashnode.com/posts/before-automating-a-business-workflow-map-the-exceptions/6aed2fb3163419921c314d17)

[Amelia Hernandez](https://hashnode.com/@ameliaconecto)

[5h ago](https://hashnode.com/posts/before-automating-a-business-workflow-map-the-exceptions/6aed2fb3163419921c314d17/comment/6af4b8dc671d03f826e013bc)

I like the distinction between a retryable connection problem and a policy question, because they need different next steps. For a lead follow-up workflow, I’d also record the last contact date and a simple duplicate rule before allowing a retry. That gives the reviewer enough context to decide whether to follow up or leave the record alone.