This SAS KB article contains structured instructions for diagnosing and resolving problems in SAS Micro Analytic Service. 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 Micro Analytic Service on the SAS Viya Platform. For SAS Micro Analytic Service on SAS^® Viya 3.5^®, see SAS KB0046157.

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 publishing to SAS Micro Analytic Service or executing a module within SAS Micro Analytic Service?
• If the problem occurs when publishing to SAS Micro Analytic Service, which application are you publishing from?
• If the problem occurs when executing a module within SAS Micro Analytic Service, what do you use to execute the module? (For example, SAS^® Event Stream Processing, a REST client, or some other client application.)
• How many modules are published to SAS Micro Analytic Service?
• Which version of SAS Viya (cadence and release) do you use? (For example, 2026.03 LTS or 2026.06 Stable.)

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?
• Is the issue consistently reproducible?

Scope of Impact

• Does this issue occur for all models or decisions or only specific models or decisions?
  • Have you tested with other models or decisions?
  • Have you tested with a simple model or decision?
• Does this issue affect all users or only certain users? If the issue effects only a certain user, 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 models, decisions, or modules.)

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 (SAS KB0038941)
• 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

If you are unable to provide the get-k8s-info output, then, at a minimum, collect a describe and the logs from the time of the issue from the relevant pods using the correct command for your Kubernetes version.

kubectl -n viya describe <pod> 
kubectl -n viya logs <pod> 

• Publishing to SAS Micro Analytic Service:
  • sas-microanalytic-score-*
  • sas-model-publish-*
    
    
• Executing within SAS Micro Analytic Service:
  
  • sas-microanalytic-score-*
    
    
• Executing Decisions that Use Advanced Lists Within SAS Micro Analytic Service:

  • sas-microanalytic-score-*

  • sas-list-data-*

  • screenshots of properties from SAS^® Environment Manager:

    • SAS Environment Manager ► Configuration Items ► All Services ► sas.commons.redis.servers 

    • SAS Environment Manager ► Configuration Items ► All Services ► sas.listdata.redis

  • the host name, port, and architecture of the back-end Redis Server used for Advanced Lists

Optional or Additional Data

If SAS Micro Analytic Service is connected to a database, provide the connectionstring that is configured within SAS Environment Manager to make that connection.

Note: Remove any sensitive information (such as user names or passwords) from the connectionstring.

Providing complete data up front reduces resolution time.

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.