Recover from a Help, save, import, chart, or analysis problem

Protect the saved plan before trying to repair the symptom

If a request did not finish, reload the original plan or conversation and check the saved values or messages before trying again. A delayed response can arrive after a change was saved, so do not repeatedly submit the same action.

When a page will not load, a save appears missing, a chart is blank, an import fails, or an analysis remains queued or errors, begin by confirming the selected plan and the last value that was actually saved. An unsaved draft and the last saved plan can look similar while representing different states.

Before reloading an editor, keep a note of unsaved changes. If one report section fails while other information is visible, use its Retry action when offered. Report a repeated failure rather than changing financial inputs to make the panel load.

Do not repeatedly submit an expensive analysis or repeat a destructive import choice while the first request may still be active. Read the visible message and preserve the question you were trying to answer.

Correct a named input before treating the result as a defect

A disabled action usually means a required choice, valid input, access level, saved plan, or analysis state is missing. Read the explanation near the control. A large result change after a small edit can also be real when the edit crosses a retirement, benefit, tax, healthcare, depletion, or guardrail boundary.

A blank value or NaN is never an expected financial result. If a holding has no verified quote, check its symbol and enter a supported manual value from a current source; do not interpret a missing price as a worthless asset. A maintenance page means ordinary planning access is temporarily unavailable.

If the same problem remains after the saved input is confirmed and the page is reloaded, open Feedback & support and report it with the page name, approximate time, action, and safe error reference.

Return to the last trustworthy checkpoint

For a save problem, reload the same plan and reopen the section. If the value did not return, it was not safely saved. For an import, return to preview and check source format, account mapping, warnings, and merge versus replacement. For an analysis, review whether the work is queued, running, completed, cancelled, or errored on its owning page. Then use Feedback & support from the account menu if the problem remains.

Rerun only after confirming the saved inputs and assumptions. For a visual problem, check whether the same information is available in labels, a table, print, or export, then report the inaccessible presentation rather than guessing from color or a missing chart.

If a display problem continues after reload, try another current browser to see whether it is specific to that browser. Preserve unsaved work before clearing site data, and confirm that you can sign in and reopen the saved plan first.

Verify recovery by reopening the evidence

A recovery step succeeds only when the saved page can be reopened and the intended value remains, or when the analysis reaches a clear completed state for the correct plan. A message disappearing is not enough.

Action confirmations and failed-attempt messages can be dismissed and do not repeat on reload. Their disappearance is not proof that a failed save succeeded. Result warnings remain while their cause applies, even when their details are hidden to recover page space.

Keep protected diagnostics private. Help cannot inspect your saved financial information while you are signed out and support should not ask for a password, authentication code, or complete financial record.

Check that a validated market-data batch was saved

Source validation checks the supplied files; a successful commit publishes the complete dataset. Check the saved security count, source date and successful refresh before using it. Complete Fidelity universes are supported. A validation report alone does not mean the dataset was saved.

If saving fails, the previously saved dataset remains available. Keep the complete source batch and validation report, and report the failure through Feedback & support. Never omit securities and describe the remainder as a complete dataset.

Give support the details needed to find the problem

Use Feedback & support and include the page name, approximate time, action you tried, and displayed error reference when available. Explain what you expected and what happened. A balance or result question should identify the plan and relevant year without including full financial documents.

No additional download is needed to send a problem report. Never send a password, authentication code, recovery secret, or brokerage login. Keep replies on the existing support conversation so the context stays together.