The automation that pays for itself in a fortnight
Most teams start with the wrong task. The one worth automating first is rarely the one that annoys people most.
8 MIN READ
Retries, idempotency and dead-letter queues are not advanced topics. They are the difference between a pipeline and a rumour.
An integration that works when you test it is not an integration. It is a demonstration.
The difference shows up at 2am, when the upstream API returns a 503, or sends the same webhook twice, or sends it out of order. A pipeline without retries loses the record. A pipeline with retries but no idempotency creates two. A pipeline with both but no dead-letter queue silently drops the ones that fail permanently, and nobody finds out until month end.
None of this is advanced. It is three specific decisions, made once, at the point where two systems meet.
Most teams start with the wrong task. The one worth automating first is rarely the one that annoys people most.
A dashboard is not a deliverable. It is a bet that someone will change a decision because of what it shows.