Stingray Technology Solutions — last updated August 15, 2026
| Severity | Description | Target response |
|---|---|---|
| Critical | Production Nexus down, data loss | Same business day |
| High | Major feature unavailable | Next business day |
| Normal | Question, configuration help, minor bug | Within 2 business days |
| Low | Feature request, documentation | Within 5 business days |
/status endpoint (or a screenshot)Before opening a ticket, check the following endpoints on your Nexus deployment:
GET /health — should return 200 OK with {"status":"ok"}GET /ready — should return 200 with adapters_count > 0GET /status (requires authentication) — full startup state including DB readiness, adapter list, background task healthThe Azure portal also surfaces container logs under your Container App resource → Log stream.
Container App fails to start. Verify the per-tenant Key Vault has both acr-pull-password and signing-secret populated. The Marketplace install populates these automatically; if they are absent, the deploy did not complete.
OAuth sign-in fails. Confirm the Global Admin clicked the "Authorize Nexus" admin-consent link before installing. Without consent, end users cannot sign in.
Adapter calls fail. Secrets for third-party systems (Monday API key, NetSuite TBA tokens, MSSQL connection string, etc.) must be planted in the per-tenant Key Vault under names like MONDAY.bridge.token. See support@stingraytechnologysolutions.com for the credential planting walkthrough.
Stingray Technology Solutions
Email: hello@stingraytechnologysolutions.com