Troubleshooting and support
Recover interrupted work and collect useful support details.
Check these things first#
- Confirm the account and workspace in the account menu.
- Read the inline message and note the project and revision.
- Finish or cancel the active local edit before starting a different workflow.
- For an existing request, use its displayed status check rather than submitting a duplicate.
- Reopen the project to distinguish a saved result from a local draft.
Common situations#
| What you see | What to do |
|---|---|
| Project missing | Check workspace, search and archived/status filters. |
| Context required | Open Project settings, save Presentation context, then review and continue the retained draft. |
| Build or export disabled | Read the availability message. Saved-revision preview builds are available. Read the displayed reason if a control is disabled. Native CLM package preparation is currently unavailable; existing authorized exports can still be checked. |
| Object cannot be edited | Check locks, another active edit and whether the object is code managed. |
| Attachment incomplete | Refresh its processing status and review partial excerpts before using them as evidence. |
| Preview shows an earlier result | Check the build’s candidate or saved revision identity against the current project. |
Recover an uncertain request#
A timeout does not prove that the server rejected your request. Keep the current browser session and use the relevant control: Check saved build, Check saved export, Check acceptance or the panel’s saved-operation check.
Use an offered exact-request retry to reconcile the retained operation. Do not clear browser storage as a first troubleshooting step: it can remove the retained request information needed for recovery.
Collect useful diagnostics#
Open Author help, then Get help with this context. Load the diagnostic identifiers and choose Copy IDs. Include the action you took, what you expected, the actual message and whether reopening changed the result.
For a failed saved build, use Copy reference when offered. Share diagnostic IDs through your support channel; avoid sending credentials or unrelated private source files. You can also arrange a product session through the CLM Studio contact page.