A modeling task can stall for very different reasons. You might have a recurring question about an account or installation, encounter an error while working, or simply need the exact reference for a feature. Treating all three as the same kind of problem often leads to unnecessary browsing—and delays getting back to the science.
A simple first step is to identify what you need next: an answer, a fix, or a specification. That distinction gives you a practical route through SAMSON’s help resources.
Start by naming the problem
Before opening documentation, write down the question in one sentence. For example: “I need to know where to find a recurring account answer,” “Something is not working as expected,” or “I need the detailed reference for a feature.” This small pause helps separate uncertainty about how something works from a problem that needs diagnosis.
If you are not sure which category fits, begin with the FAQ. It is intended for recurring questions, including topics such as accounts, installation, updates, and extensions. If your question is not answered there—or you already know that you are dealing with a malfunction—move on rather than repeatedly searching the same general material.
Choose the route that matches your situation
- You need a quick, recurring answer: start with the FAQ. This is the most direct route for common questions.
- You have a symptom to investigate: use Troubleshooting. It is organized around diagnosing problems and following a practical fix path.
- You know the feature area and need its details: go to References. This is the better choice when you need a feature-specific reference rather than a general answer or a diagnosis.
The key is not to read every resource in order. Follow the path that fits the question you have right now. A feature reference may not help diagnose an unexpected symptom; troubleshooting may be unnecessary when you only need a canonical description; and an FAQ may not be the fastest route when the issue is already clearly symptom-based.
Make troubleshooting more useful
When you do need to investigate a problem, take a moment to describe it precisely. Record what you expected to happen, what happened instead, and the point in your work when the issue appeared. If you have already tried a step, note that too. These details make it easier to compare your situation with troubleshooting guidance and avoid repeating checks that have not helped.
Keep the question focused on the obstacle in front of you. If the issue turns out to be a question about a particular feature rather than a malfunction, switch to the relevant reference material. If it is a broader onboarding question, the Start here guide covers installation, first-use orientation, and onboarding follow-up.
When the question is about working with others or extending SAMSON
Not every question belongs in the same help path. For SAMSON Connect, permissions, groups, or shared documents and jobs, visit Share and collaborate. For scripting, extensions, and developer-facing workflows, use Automate and extend. Choosing the section by subject helps keep a collaboration or development question from getting lost among general troubleshooting material.
A useful rule to remember is: FAQ for a recurring answer, Troubleshooting for a symptom, References for feature details. It is a quick way to choose a starting point when a modeling session is interrupted, without having to browse the whole guide.
For the complete help overview, see Reference and help.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.