Skip to main content
Boermans Digital
Main menu

Best practiceAutomation

What should happen when an automation fails?

A task has started, but nobody knows whether the final step completed. Running it again feels like the quickest fix, until someone discovers that the order already exists. Recovery belongs in the process design, not just in the response to the first incident.

Example of handling exceptions and recovery.

An error message is not a diagnosis

A timeout means a response did not arrive in time. The receiving application may still have processed the instruction. Record the step that started, the confirmation received and any remaining uncertainty. An operator needs a way to compare the source with the destination.

Distinguish a temporarily unavailable connection from invalid business data. Waiting may help with the first. Repeatedly sending an unknown product code is unlikely to resolve the second.

Choose recovery based on the outcome

On a narrow screen, scroll the table sideways. With a keyboard, focus the table and use the arrow keys.

A practical decision framework, not a universal automatic restart policy.
SituationEstablish firstNext step
Temporary fault, instruction confirmed unprocessedIs repetition permitted and bounded?A controlled retry under the recovery policy.
Business exceptionWhat information or authority is missing?An owner corrects the data or makes a decision.
Outcome uncertainDoes a result already exist in the destination?Investigate and reconcile before restarting.
Incorrect processing confirmedWhich effects can be reversed?Authorised correction, not silent resubmission.

Do not turn recovery into another problem

Set retry limits and delays according to the application and process. Independent retries at several layers can multiply the work. Decide which layer owns retries. A stable task reference helps identify earlier attempts.

Test concurrent attempts and interruption immediately after a successful write. Checking whether a record exists before acting does not always prevent concurrent duplicates. Have a specialist design the protection against repeated effects.

Make the alert useful to its recipient

An alert should identify the affected process, when the problem occurred and where to find the last confirmed step. Do not attach full documents, passwords or unnecessary personal data. The aim is focused investigation, not duplication of the entire case file.

An inbox without an owner is not a recovery process. Define the responder, cover during absence and the point at which the process owner becomes involved. Business deadlines matter as well as technical error codes.

Rehearse before a real deadline is at risk

  • A connection fails before and after processing.
  • The same instruction is submitted twice.
  • An operator corrects data during a retry.
  • The usual administrator is unavailable.
  • A backlog needs to be cleared in an agreed sequence.

Check the resulting records and totals after recovery. An error disappearing does not prove that every task completed correctly.

Agree what needs to change

Review the cause, impact and recovery effort after an incident. A validation check might be missing or a warning might arrive too late. Assign a specific improvement to an owner. Limit access to incident information and agree appropriate retention. The next recovery should depend less on someone who happens to remember the workaround.

Use these recovery questions when choosing a tool too: who sees a failure, who may resume work and how is the outcome checked? Compare the strengths and considerations of the offered solutions. The required features and ongoing management need to fit the chosen setup. You can also discuss the process and open questions with Joshua first.

What would you like to clarify?

Describe the process step or open question. We can explore a practical next step together.

Discuss your process

Explore your process with the Automation Scan

Adapt this framework to your systems and responsibilities. It is not a guarantee of safety, availability or readiness.

Technical background: Microsoft Azure Architecture Center, Retry (transient failures) and Idempotent Consumer (duplicate processing); OWASP Logging Cheat Sheet, Event attributes and Data to exclude (useful event records and data that should not be logged). The decision framework is an original application.

Editorial content prepared with AI assistance. The content was reviewed by Joshua Boermans in the week beginning 12 October 2026.

Earlier versions and publication decisions

These notes concern earlier versions. They do not establish a review of the current text or an independent assessment.

Boermans Digital editorial content, prepared with AI assistance.

Approved for publication by Joshua Boermans on 3 October 2026.

A subject-matter review, including the reviewer, date and scope, has not yet been recorded.

Publication approval is not independent subject-matter validation. No independent review has been recorded.

Boermans Digital / privacy

Your cookie preferences

You decide whether Google Analytics may load. The website, scans and calculator also work without Analytics.

Completed fields, scan answers and calculator results are not sent to Analytics.

Which data and retention periods?

We remember your choice on this device for up to 180 days, including a refusal. The _ga and _ga_* Analytics cookies are configured for up to 180 days. Retention at Google is configured separately in the Analytics account.

Storage for website functionsFunctional

The website remembers your privacy choice. Only when you choose to switch language can scans, the guide and calculator temporarily carry answers within the same tab. Contact details are not stored in that transfer.

Contact form protectionAt request review

Google reCAPTCHA loads when you open the review of your completed request. Google then processes technical data and may use security cookies. This is separate from your Analytics choice. Contact by email remains available.

Analytics is off.