What this means
The correct application window was found, but multiple buttons, fields, rows, or other elements match the recorded target equally well. A coordinate fallback would still be an unsafe guess.
What to do
- Return the target application to the same screen and state used during recording.
- Select the expected tab, page, dialog, or filter.
- Reduce duplicate rows or controls when the application provides a filter or search.
- Retry playback.
- If the interface changed permanently, record the sequence again.
Why this can happen
- The screen contains duplicate controls with the same technical identity.
- A list or table now contains several equally matching rows.
- The active tab, filter, or application state differs from the recording.
- The target application changed its layout.
Example
A table contains two visually identical action buttons in matching rows. If neither has a unique identity, Offisen cannot know which one the recording intended.
Diagnostic details
| Code | OFS-1807 |
|---|---|
| Symbol | ElementTargetAmbiguous |
| Domain | Pointer and mouse |
| Layer | Target identification |
| Phase | Playback |
| Severity | Blocking error |
| Retryable | Yes |
| Privacy | Safe support context |
| Safety policy | Block before pointer input |
If the problem continues
If the intended control appears unique but OFS-1807 repeats, include the report and describe the visible layout. Candidate names or user content are not included in the report.
Include the error code, correlation ID, timestamp, Offisen version, target application when relevant, and a short description of what happened. Review the report before sharing it and remove anything you do not want to send.
Contact [email protected].