Skip to main content
Bring the exact error, solver log, study setup, and the last completed stage. Ask Adam to inspect the failure before changing the physics or rerunning an expensive job.

​
Identify the failing stage

These are starting points for diagnosis. The log and model determine which explanation is relevant.

​
Request a focused diagnosis

Investigate a failed solve
Preserve the original files and logs. Changing several settings at once can make it difficult to tell which correction mattered.

​
Retry deliberately

Test one proposed correction
Do not loosen quality or convergence criteria solely to obtain a success message. Explain what a changed criterion means for the result.

​
Recover from interruptions

A lost connection or timeout does not establish that the native operation stopped. Ask Adam to inspect the application’s current state and retained outputs before repeating an edit or solve. Native cancellation support varies; verify the solver actually stopped before starting another job. For setup failures, see Native CAE connections. For interpreting a completed run, see Results and comparison. If you need support, include the task URL, application and version, time, and non-secret diagnostics.
Last modified on October 14, 2026