---
title: "Developer troubleshooting"
description: "Useful commands: sota status, sota logs, sota manifest diff <left> <right>, and sota docs."
url: "https://sotaagents.ai/manual/developer-guide/developer-troubleshooting"
generated_by: "sotaagents-ldp"
docs_index: "https://sotaagents.ai/manual/llms.txt"
locale: "en"
---

# Developer troubleshooting

| Symptom | Check |
| --- | --- |
| Native app entry returns 401/403 | Do not call package assets directly. Confirm the UI is mounted through the platform and the exact environment is installed, enabled, and authorized. |
| Native app entry returns 404 | Confirm the artifact contains the declared entry/chunk/CSS/locale path and the selected environment points to that exact artifact. |
| AppData or tools are unauthorized | Verify actor membership, owner/contributor rules for Staging, workspace enablement, signed request validation, and environment-scoped credentials. |
| Manifest change is ignored | Use only `local`, `stg`, or `prod` overlays; run `sota validate`; increment the version before deploying changed bytes. |
| Staging works but Production fails | Compare environment bindings, secrets, health, CORS, external data stores, and installation/visibility—not only source code. |

Useful commands: `sota status`, `sota logs`, `sota manifest diff <left> <right>`, and `sota docs`.