This SAS KB article contains structured instructions for diagnosing and resolving problems in SAS Model Studio. The information in this article will help you define the problem clearly, collect essential diagnostic data, and identify the next steps toward resolution. 

The sections below outline standard data collection practices along with key questions to help define and scope the problem effectively. Establishing a detailed and complete problem description early in the investigation process can significantly reduce time to resolution. 

Note: This guide is designed for SAS Model Studio on the SAS Viya Platform. If you use SAS Model Studio on SAS^® Viya^® 3.5, see SAS KB0046154.

Define the Problem

Use the questions below to help clearly define the problem before collecting diagnostic data.

Context and Observations

• What were you doing when the problem first occurred? For example, were you creating a project, or were you running a pipeline?
• Which part of SAS Model Studio were you working in? Provide a screenshot if possible. 
• Which type of SAS Model Studio project were you using? For example, were you using a SAS^® Visual Data Mining and Machine Learning project, a SAS^® Visual Text Analytics project, or a SAS^® Visual Forecasting project?
• Which version of SAS Viya (cadence and release) do you use? For example, do you use 2026.03 LTS, 2026.06 Stable, or something else?

Error or Unexpected Behavior

• Was an error message displayed?
  • If yes, provide the full message and a screenshot if possible.
  • If no error was displayed, what unexpected behavior occurred?
• What occurred versus what did you expect? Provide a screenshot if possible.

Steps to Reproduce

• What sequence of steps led to the problem?
• Can you reproduce the issue consistently?

Scope of Impact

• Does this issue occur for all projects or pipelines or only specific ones? Have you tested other projects or pipelines?
• Does this affect all users or only certain users? Have other users attempted the same action? 

History and Changes

• Has this worked previously? If so, when was it last successful?
• Were there any recent changes? (For example, deployments, updates, configuration changes, data changes, or changes to projects or pipelines.)

Diagnostic Data to Collect

To support resolution, collect the following diagnostic data at the time that the problem occurs.

• output from the get-k8s-info script (SAS KB0038941)
• a HAR file from the browser during the issue (SAS KB0036430)
• screenshots of observations, errors, or unexpected results

If get-k8s-info Is Not Available

Collect logs from relevant services:

• All Project Types:
  • sas-analytics-*
    sas-compute-*
• SAS Visual Data Mining and Machine Learning Projects:
  • sas-data-mining-*
• SAS Visual Text Analytics Projects: 
  • sas-text-*
• SAS Visual Forecasting Projects:
  • sas-forecasting-*

Optional or Additional Data

• project logs (Advisor, Partition, and so on)
• (for issues with a specific node within a pipeline) the Node log if available 
  • Right-click the problematic node in the pipeline and choose Log.
• browser console logs

Providing complete diagnostic data in advance can significantly reduce time to resolution.

Next Steps: Navigate Resolution Paths

Once you clearly define the problem and collect diagnostic data, engage SAS Technical Support for further assistance. Provide the detailed and complete problem description along with the prescribed diagnostic data.