Troubleshooting
Connection and access
Run the connection smoke test to separate service reachability from authenticated access.
| Symptom | What to check |
|---|---|
| Health request fails | Network access, endpoint, and service status. |
401 auth_failed | Key and environment. Stop automated requests before correcting them. |
403 insufficient_scope | Required scope in the response and account access. |
429 auth_lockout | Stop the failing client, fix its key, and wait the full retry delay. |
429 rate_limited | Wait the full retry delay, then reduce request volume. |
Persistent 503 | Environment configuration and service availability; contact support with the error. |
Use Errors and limits for thresholds and retry rules. Do not loop on a rejected key.
Telemetry does not appear
- Confirm ingestion access is enabled and the key has
telemetry:writeandtopology:read. - Inspect the write response for rejected records.
- Include
entity_idand a UTC timestamp in each record. - Read a freshness window that includes the sample's timestamp.
- Keep a field's type consistent across producers and transports.
For an agent installation, run sudo constellation-agent verify and inspect sudo constellation-agent logs. See Fleet agent troubleshooting.
Predictions are empty or fail
Use a supported horizon and link ID. For live SNR, publish recent snr_db, elevation_deg, azimuth_deg, and slant_range_km with the required link tags. Confirm the model is enabled for the environment. Follow the prediction contract for the feature window and error-specific actions.
Saved work is missing
Reports, charts, scenarios, and assistant history are stored in your browser profile. Open the console in the same browser profile where you created the work. Export reports you need on another device.
Contact support
Email contact@constellation.space with the endpoint, time, status code, error body, and incident ID if present. Remove API keys and sensitive telemetry from logs before sharing them.