Blog · Topic
Automation
Writing from Sawhorse Engineering on automation.
- Articles
- 7
- Category
- Topic
- 26 September 2026Recurring dog walks with exceptions that do not duplicateSeparate a standing walking arrangement from each visit so holidays, cover and one-off changes do not corrupt the next week of work.
- 26 September 2026Site consumables replenishment without duplicate ordersConnect site counts, approved replenishment and delivery receipts while keeping requested, ordered and available stock separate.
- 15 September 2026Idempotency: the idea that prevents duplicate everythingA lost response can turn a reasonable retry into a duplicate order, email or charge. Idempotency helps, but its boundary must include the actual effect.
- 13 September 2026Automations that stop when the customer repliesThe most damaging automation failure is not a missed send. It is a sequence that keeps chasing someone who already answered.
- 10 September 2026When to use an orchestrator and when to write codeA workflow tool and a service solve the same problems differently. Four criteria that settle which one a specific process needs.
- 8 September 2026Dead letter queues, and why silence is the worst failureA failed integration needs a visible recovery path. Retry budgets, failed work queues and reconciliation prevent errors from disappearing into logs.
- 23 August 2026Reconciliation: the job that runs when nothing is wrongScheduled comparisons can find missing or inconsistent records even when no request reported an error.
Let’s talk about the system you need.
Tell us where the current process breaks down. We can map the workflow, examine the integration requirements and define a practical scope for the build.
- A mutual NDA is signed before project details are shared.
- Scope is fixed in writing before any build starts.
- You own the source code, the IP and the documentation at delivery.
- Support plans are available and tailored on a discovery or technical call.