What this means
Windows can silently remove a low-level input hook when its callback takes too long. Continuing could cause Offisen to miss keyboard or mouse events, so the affected recording or playback is stopped.
What to do
- Try the recording or playback again.
- Close applications that intensively monitor the keyboard or mouse.
- Pause heavy background work and check whether the computer is under unusual load.
- If the problem repeats, restart Offisen and copy the support report.
Why this can happen
- Another hook-based application delayed the global input chain.
- Security, accessibility, keyboard, mouse, overlay, or remote-control software was busy.
- The system experienced a temporary performance stall.
- Offisen’s own callback processing exceeded the effective timeout.
Example
Several utilities monitor every keystroke while the system is under heavy load. One callback returns too late, so Offisen stops rather than continue with a hook Windows may have detached.
Diagnostic details
| Code | OFS-1903 |
|---|---|
| Symbol | HookCallbackExceededLimit |
| Domain | Hooks and runtime health |
| Layer | Input capture |
| Phase | Recording or playback |
| Severity | Blocking error |
| Retryable | Yes |
| Privacy | Safe support context |
| Safety policy | Stop active operation |
If the problem continues
If the error is repeatable, include the report and list any keyboard, mouse, accessibility, security, overlay, remote-desktop, or automation tools that were running.
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].