Resilience and failure handling
Resilience does not mean that failures never happen, but that it is known in advance what happens when an element of the workflow fails. This page is a list of decisions to make during deployment, not a promise of specific operating parameters.
- Intent
- Input control
- Authorization (applies)
- AI (applies)
- Result validation
- Human
- Evidence
Highlighted: the points of the flow that this description refers to. Orange marker: a human decision at this point.
Control does not disappear when something fails
The most important decision concerns the order of things: if the check cannot be performed, the operation should not be performed by bypassing it. Technically, this is called the fail-closed principle. Its opposite, fail-open, means continuing work without the check.
| Situation | What to decide during deployment | More |
|---|---|---|
| The model or its provider is unavailable | Whether the task waits or switches to a fallback model, and whether the fallback model is approved for the same data zone. | Model selection |
| The check before sending cannot be performed | Whether the query is held until the check is restored (fail-closed). For data designated as sensitive, continuing without the check increases the risk of disclosure. | Boundaries in the workflow |
| An AI digital worker acts incorrectly or approaches its limits | Who can suspend or revoke its agent passport, and which operation and cost limits to adopt. | Accountability for decisions |
| No Internet access | Whether the process is to work offline. This requires local models and all the services needed in the process, including search and OCR if they are used. | Working without the Internet |
| Server failure in your own infrastructure | Backups, the way of restoring and updating, and the person responsible for maintenance. | On-premise deployment |
| You need to find out what happened | Who has access to the evidence trail and how long it is kept. The organization sets the evidence retention period. | Documenting the workflow |
Conditions, transitions and decisions
Diagram of the controlled run
- Step 1: DetectionAn element of the workflow reports an error, unavailability or a limit being exceeded.
- Step 2: ConditionCan the operation be completed without skipping the check and within the zone’s boundaries?
- Step 3: DecisionIf yes, the workflow continues according to the agreed procedure. If no, the operation is held.
- Step 4: Limiting the impactIf needed, an authorized person suspends or revokes the agent passport under which the AI digital worker operates.
- Step 5: InvestigationThe workflow is reconstructed from the evidence trail, and the procedure is corrected.
Suspending and revoking an AI digital worker
Actions in the agent passport
The view of the agent passport under which the AI digital worker operates has the “Suspend passport” and “Revoke passport” buttons. They are used to limit the impact when the AI digital worker acts incorrectly.
The screenshot shows AiTrust on synthetic data and is a separate configuration example, unrelated to the recorded complaint run.
What the screenshots show
- The suspend and revoke actions available in the passport view in this example.
What the screenshots do not prove
- The effects of suspension during an operation in progress.
- How the system behaves when a model, the network or a server fails.
- Availability parameters (maintenance terms are agreed for each specific deployment).
On-premise and resilience
An on-premise deployment in the customer’s infrastructure means that continuity of operation also depends on the organization’s infrastructure: servers, backups and the way updates are applied.
An on-premise deployment alone does not determine whether work without the Internet is possible. That depends on the configuration and the dependencies of the given process. Details: Working without Internet access.
Related areas
Methodologies and compliance
Let’s discuss failure scenarios for your deployment
In the demo, we will go through the list of failure situations and identify the decisions that need to be made for your infrastructure and processes.