What this means
The Windows lock screen uses a secure desktop. Offisen cannot safely observe recording input or deliver playback input while that desktop is active, so the current operation ends.
What to do
- Unlock Windows.
- Check that the target application is still open and in the expected state.
- Start the recording or playback again manually.
- For long unattended runs, review the Windows idle-lock policy if organizational rules permit changes.
Why this can happen
- You pressed Windows + L.
- Windows locked automatically after an idle timeout.
- A company security policy or remote-session event activated the lock screen.
Example
If Windows locks while a sequence is paused or playing, Offisen stops that run. Unlocking Windows does not silently resume input; you choose when to start again.
Diagnostic details
| Code | OFS-1602 |
|---|---|
| Symbol | SessionLocked |
| Domain | Session and secure desktop |
| Layer | Security and session |
| Phase | Recording or playback |
| Severity | Blocking error |
| Retryable | Yes, after unlocking |
| Privacy | Safe support context |
| Safety policy | Stop active operation |
If the problem continues
No support action is normally needed for an expected lock. If Windows locks unexpectedly or Offisen behaves differently after unlock, keep the report and note how the lock was triggered.
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].