When updating design points in a parametric study sequentially and capturing simulation report data, a simulation report-related state file will be written to the current simulation directory of the project folder, rather than in the simulation report folder. The file does not get registered with the project, and can be ignored or deleted without any issues.

When saving parametric projects on Windows, the Save As Copy command can be problematic if there are too many characters in the project directory (> 170 characters).

Parameters are not yet supported in Fluent in meshing mode

Graphical interactions within the Parametric Study window and the Project View are not captured while recording journals.

When updating local parametric runs concurrently, you cannot update design points when the base session is launched in distributed mode.

Design points created in optiSLang cannot be updated in batch mode on Linux where the graphical user interface is not available.

When you export your simulation report as a PowerPoint presentation, named expression tables, that can be long and extensive, are not automatically split across multiple slides.

If multiple report definition monitors are combined into a single report file, not all of the monitors may appear in the monitor plot accessed from the Parametric Design Table context menu. This can be avoided by placing the data for each monitor into its own report file.

If parametric projects are given long names and/or placed deep in a directory structure, problems may occur due to limitations in the length of the file path (for example, the Windows filepath limit is ~256 characters).

If you choose to stop the processing of a batch of design point updates through optiSLang optimization, the individual design point status may be designated as failed in Fluent, even for those design points that were previously completed. This is because the optiSLang server no longer retains the outputs for any design point updates that have already been completed.