What this means
Windows can reuse a numeric window handle after an application or window closes. Offisen detected that the reused handle belongs to a different process than the one recorded and blocked playback.
What to do
- Make sure the application used during recording is running.
- Open the intended window and return it to the expected state.
- Retry playback so Offisen can resolve the correct live target.
- If the recorded application or workflow has changed permanently, record the sequence again.
Why this can happen
- The original target window was closed.
- Windows reused its old handle for another application.
- A transient window or popup disappeared between recording and playback.
- The resolved target no longer matches the recorded process identity.
Example
A recorded application is closed, and much later Windows assigns its old handle value to another program. Offisen recognizes the different process name and refuses to activate that window.
Diagnostic details
| Code | OFS-1805 |
|---|---|
| Symbol | TargetProcessIdentityMismatch |
| Domain | Window activation and focus |
| Layer | Target identification |
| Phase | Playback |
| Severity | Blocking error |
| Retryable | Yes |
| Privacy | Safe support context |
| Safety policy | Block before activation |
If the problem continues
If the correct application is running and this code repeats, keep the report. It contains the expected and current process names and the window handle, but not window titles or document content.
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].