What this means
No more specific diagnostic guard classified the failure. This is a fatal catch-all error, so Offisen stops ongoing automation and may require a restart.
What to do
- Copy the support report before restarting Offisen.
- Review the report and remove anything you do not want to share.
- Restart Offisen using the dialog action when available, or close and reopen it manually.
- Check whether the same action causes the error again.
- If it repeats, contact support with the report and a short description of what happened immediately before the failure.
Why this can happen
- An unexpected exception reached a global application error handler.
- A background task failed without a more specific diagnostic classification.
- The application encountered an internal state it could not continue from safely.
Example
An unexpected exception occurs during playback and no specialized guard recognizes it. Offisen stops playback, preserves a bounded technical summary, and asks you to restart rather than continue in an uncertain state.
Diagnostic details
| Code | OFS-9001 |
|---|---|
| Symbol | UnexpectedInternalFailure |
| Domain | Internal |
| Layer | Diagnostics and support |
| Phase | Internal; affected operation may be recording, playback, or none |
| Severity | Fatal |
| Retryable | No; restart and investigate |
| Privacy | Requires consent |
| Safety policy | Stop active operation; restart may be required |
If the problem continues
The report may contain the exception type, message, and stack trace. These details can include local paths, usernames, or incidental machine-specific information. Review the report carefully and share it only with your consent.
Include the error code, correlation ID, timestamp, Offisen version, and what you were doing immediately before the error.
Contact [email protected].