Scope
Oto depends on cloud services, external providers, branch services, and installed devices. Workflows show whether the required service is available and whether an interrupted action completed.
Design
Users can see when a required service or device is unavailable. Where a source workflow supports retry, reconciliation, fallback, or later completion, Oto presents that action without creating a duplicate result.
Failure handling
An unavailable dependency does not present an uncertain action as successful. The workflow shows whether the action failed, remains pending, or requires review.
Requirements
- Affected workflows show when required cloud, provider, branch, or device services are unavailable.
- Users can review interrupted actions that require retry or reconciliation where the source workflow requires it.
Verification
- Test the user-visible unavailable and interrupted states required by each applicable workflow.