DUBSAR for operations
Role · COO / Operations leader
An AI workflow has stopped. What should happen next?
A request to create an order has been sent to an ERP. The workflow stops before the team receives a usable confirmation. Should someone wait, investigate or try again?
For the operations lead, the immediate priority is to preserve completed work and prevent uncertainty from triggering a second action by default. This guide sets out a decision process to adapt with the integrator and the team running the workflow. The ERP scenario is illustrative; it does not announce an available DUBSAR connector.
In brief
The question and the useful result.
- Question
- How do you decide what happens next after an interruption whose outcome remains uncertain?
- Useful result
- A decision path and a handover note that can be passed on.
DUBSAR for operations
1. Establish what is known before trying again
Reconstruct the last verifiable state. In this example, four pieces of information need to remain separate:
| Item | What the team can establish |
|---|---|
| Request | Create the order for the selected case. |
| Authorisation | This creation was permitted within a defined scope. |
| Attempt | A request was sent to the external system. |
| Outcome | The order’s actual creation has not yet been confirmed. |
An acknowledgement records one stage of an exchange. Its meaning depends on what the service confirms: the request may have been received without the order’s creation being established.
Recording “outcome to be verified” preserves useful information. Marking the operation as successful or failed too early may lead the next team to make a decision from an incomplete picture.
DUBSAR for operations
2. Make the next step explicit
Pause further attempts of the action in question while its outcome is checked. Identify someone with the appropriate access to inspect the result in the external system, then gather the references they need.
The next decision depends on what the investigation actually establishes:
| Established situation | Decision to prepare |
|---|---|
| The intended effect is confirmed. | Continue from that result without repeating the completed action. |
| Failure with no effect is confirmed. | Examine the cause and the conditions for a new attempt. |
| The outcome remains uncertain. | Keep the uncertainty visible and assign further investigation to a named person. |
| Authorisation no longer covers the proposed action. | Obtain the required decision before taking a new action. |
An order missing from a partial search does not establish that the operation failed without effect. Record what was checked and what the check supports.
Before another attempt, review the exact action, its parameters and the applicable authorisation. Human approval may be required by the process rules. The recovery decision should identify the step to resume and the previously confirmed operations that must not be repeated.
DUBSAR for operations
3. Leave a usable handover
A different team should be able to continue the investigation without reconstructing the entire conversation with the agent. Prepare a handover note covering:
- the mission’s objective and its last confirmed step;
- the action in question, its authorisation and the reference for the attempt;
- the evidence reviewed and the remaining uncertainties;
- the next check, the person assigned to it and the decision still needed.
Keeping an action on hold can be a justified operational decision. Its reason, follow-up and conditions for resuming need to be clear.
DUBSAR for operations
4. Where DUBSAR is intended to help
DUBSAR is developing a governance foundation to retain mission state, link actions to authorisations and preserve available evidence with its limits. The aim is to help teams hand over and resume work while accounting for uncertain outcomes, alongside their existing tools.
Components and selected workflows have been tested. Full B2B integration and validation are still underway. Pilots are not currently open.
DUBSAR for operations
Frequently asked questions
Does a missing response mean the action failed?
It is not enough to establish failure. Look for evidence of the actual effect and retain the uncertainty when that evidence is missing.
Should the entire workflow be restarted?
First identify the step to resume and the outcome of each action already attempted. Restarting a workflow must not implicitly repeat earlier effects.
Would DUBSAR replace operations monitoring?
Its intended role concerns agent missions, authorisations and evidence. Business monitoring and technical investigation tools remain part of the workflow.
DUBSAR for operations
Continue reading
DUBSAR for operations
Explore the project and its current status
Learn how DUBSAR aims to support continuity across agent missions and where development stands today.