This SAS KB article contains structured instructions for diagnosing and resolving problems in SAS Model Manager. 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 Manager on the SAS® Viya® Platform. For SAS Model Manager on SAS® Viya® 3.5, see SAS KB0046155.
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 working with a model or a project? Were you validating a model with a scoring test? Were you publishing a model to a destination?
- Which part of SAS Model Manager were you working in? Provide a screenshot if possible.
- Which version of SAS Viya (cadence and release) do you use? For example, are you using 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 issue?
- Can you reproduce the issue consistently?
Scope of Impact
- Does this issue occur for all models and projects or only specific ones? Have you tested other models or projects?
- Does this issue 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, updates, configuration changes, data changes, or changes to models.)
Diagnostic Data to Collect
To support resolution, collect the following diagnostic data at the time the problem occurs.
- output from the get-k8s-info script
- a HAR file from the browser during the issue (SAS KB0036430)
- screenshots of observations, errors, or unexpected results
You should provide these artifacts in addition to a clear problem description.
If get-k8s-info Is Not Available
Collect logs and describe output from relevant pods:
Optional or Additional Data
Providing complete diagnostic data up front 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.