This page groups the 721 published deployment and environment documents by the stage at which the problem appears. Use it to narrow down the stage first, then open the list for that stage to find the specific document. Grouping follows the technical objects named in document titles.
Narrowing down: three steps
| Step | What to confirm | Points to |
|---|---|---|
| 1 | Whether the service process started, and the state of container and orchestration components | Process not up → containers and orchestration, images and architecture; process up but unreachable → startup and reachability |
| 2 | Whether backend logs show connection errors from dependencies (database, object storage, inference service) | Database or storage errors → databases and object storage; model call errors → model serving and inference |
| 3 | Whether the problem appeared after a version or configuration change | After a change → upgrades and migrations, environment and configuration; unrelated to a change → follow the conclusion from steps 1 and 2 |
Stages, how to tell them apart, and document counts
| Stage | How to tell | Published documents | List |
|---|---|---|---|
| Images and architecture | container image retrieval and processor architecture | 13 | Search Technical Center |
| Containers and orchestration | container runtime and orchestration | 18 | Search Technical Center |
| Databases and object storage | database connections and object storage | 17 | Search Technical Center |
| Upgrades and migrations | the upgrade process and behaviour after upgrading | 114 | Open list |
| Environment and configuration | environment variables and configuration files | 125 | Open list |
| Startup and reachability | service startup and reaching the service | 13 | Search Technical Center |
| Model serving and inference | self-hosted inference services and model integration | 41 | Open list |
| Agent and MCP | agent runtime, sandbox and MCP tooling | 29 | Search Technical Center |
| API and authentication | API calls and authentication | 33 | Open list |
| Workflow and nodes | workflow orchestration and node configuration | 37 | Open list |
The five stages with lists cover 350 documents. Another 281 documents cover more scattered topics and are not yet grouped into a stage; they can be found by searching for the specific error text.
Three ordering mistakes to avoid
- Changing configuration before reading logs. Most deployment problems name the component and the error code in the backend log. Adjusting environment variables or orchestration files before reading the log removes the baseline for everything that follows.
- Going straight to the main service and skipping its dependencies. When the database, object storage or inference service is unreachable, the main service looks broken in every case, so starting there leads nowhere.
- Not separating before and after a change. A problem that appeared after an upgrade or configuration change follows a different path from one that appeared during steady operation; confirming the time relation halves the search space.
Checks before go-live and before any change
- Confirm every environment variable added or removed by the target version has been handled
- Confirm each companion component image matches the main service version
- Confirm database and object storage connection details work in the target environment
- Confirm the processor architecture matches the selected image
- Confirm the inference service is reachable from inside the deployment network, and complete one call to verify
What this landscape does not cover
Grouping follows the technical objects named in document titles. A document may touch several stages; it is placed in the first stage it matches. The following are outside the scope of this page:
- Deployment forms and configuration specific to the commercial edition
- Network and permission setup coupled to a specific cloud provider
- Performance and capacity questions that need runtime data to judge
Keep reading
References
If the problem is still not located
The entries above cover cases that can be reproduced from public information. If the problem depends on configuration details of a specific deployment, or needs runtime logs to confirm, contact sales for deployment-stage support; the cloud service can be used directly without handling environment dependencies.
- Contact sales: support for self-hosting and upgrades
- Get started: use the cloud service and skip environment setup
- Pricing: compare what the cloud and self-hosted forms cover