Troubleshooting

Start with the symptom below, try the smallest safe fix, and preserve the current file before a destructive recovery.

A project or file is missing#

1. Confirm the correct project is open.
2. Search the project sidebar and expand the parent folder.
3. Verify that the file still exists inside the local project folder.
4. If another app created or moved it, refresh or reopen the project.
5. If it was just deleted in Nebula Writer, use the delayed Undo action before it expires.

Files outside the open project are not shown in its tree. Hidden or unsupported files may also be omitted.

The agent is not responding#

Check sign-in, network connectivity, and the account usage state. Then try a small request against the active document:

Summarize the active document in three bullets. Do not edit it.

If that works, the original request was likely too broad or depended on missing context. Add the specific file with @ or as an attachment and split the work into stages.

The agent used the wrong source#

Discard any pending review, start a new chat when necessary, and name the source of truth:

Use only the Approved Forecast table in the Summary sheet of @forecast.xlsx. Ignore prior estimates. List the values you will use before editing any file.

Do not accept a partly correct change and try to repair it blindly. Recover the clean state, then rerun a narrower request.

A generated file does not appear#

• Check the agent response and modified-files summary for the exact path.
• Expand the destination folder in the project tree.
• Use a filename with a supported extension.
• Ask for a new output path instead of overwriting an open source file.

Create exports/decision-brief.docx. Do not overwrite an existing file. Report the exact path and every source you used.

A DOCX layout changed#

Inspect the affected pages, headers, footers, tables, images, and page breaks. Use Discard All while the agent review is pending, action history for a recent agent operation, or version history for a saved DOCX state.

For strict compatibility, reopen the recovered file in Microsoft Word. Nebula Writer does not reproduce every advanced Word review or layout feature.

A workbook result looks wrong#

Check the formula bar, sheet names, cross-sheet references, filters, hidden rows or columns, number formats, and chart ranges. Read any structural or formula warning before saving.

Recalculate the workbook in Excel when the result depends on specialized formulas or exact compatibility. CSV cannot preserve formulas, multiple sheets, charts, or formatting.

A presentation looks different after an edit#

Run the deck audit and inspect every affected slide for overflow, object position, image crop, alignment, layers, and notes. Discard a broad pending review and rerun it on a smaller slide range.

Nebula Writer does not export PPTX to PDF. Verify the final deck and export in PowerPoint or another compatible presentation app.

LaTeX will not compile#

Read the first actionable diagnostic and check its file and line. Fix one error at a time, then compile again.

Explain the first actionable LaTeX diagnostic and the smallest safe fix. Do not edit the source or enable shell escape.

The preview can show the last successful PDF after a later failure. Trust the compile status, not the visible page alone.

If the project needs packages or auxiliary tools not available in the bundled workflow, install the optional managed TeX Live environment. Recommended covers common packages and usually takes 5–15 minutes; Full is roughly 10 GB and often takes 20–60 minutes or more.

LaTeX asks for shell escape#

Do not enable it automatically. Shell escape lets the project run external commands with your user permissions. Inspect the source and dependencies first, and enable Trusted shell escape only for a project you trust. It requires TeX Live.

A shared file is stale or read-only#

• Confirm you are signed in and online.
• Check whether the folder role is owner, editor, or viewer.
• Confirm the account has Pro cloud write access.
• Wait for save or sync to finish, then reopen the shared file.

Free users can accept shared-folder invites, but editor invitations remain read-only without Pro cloud write access.

Recover an earlier state#

Use the least disruptive option:

1. Discard a pending review.
2. Undo a recent agent action from action history.
3. Compare and restore a saved document version.
4. Recover from your external backup or version-control system.

Review changes & recover explains what each history surface covers.

Report a reproducible problem#

Include the app version, operating system, file type, local or shared state, exact error text, and the shortest steps that reproduce the issue. Remove personal content from screenshots and sample files before sharing them.