Release review
Reply by submitting a higher version that addresses every review note. If a pending review exceeds five business days, the platform creates an SLA event automatically.
Developer support
A trackable path when releases need help.
Use Developer Console so the ticket is attached to your organization, app, release history, health, and contact details. Review events and SLA alerts appear in the same Console activity feed.
Choose the right channel
Product support
Create a normal ticket for SDK, manifest, Bridge, Console, analytics, rollout, ownership, or policy questions. Include app ID, version, environment, and reproduction steps.
Production incident
Use high severity for widespread errors or unavailable functionality. Disable or roll back the release immediately from Console when user impact is continuing.
Security incident
Use critical severity for active compromise, credential exposure, unsafe data access, or a Textxt vulnerability. Do not include secrets in the ticket body.
Response targets
| Severity | Use when | Initial response target |
|---|---|---|
| Critical | Active security or severe platform-wide incident | 8 hours |
| High | Production app is broadly unavailable or corrupting user work | 24 hours |
| Normal | Review, SDK, integration, ownership, or analytics issue | 3 business days |
| Low | Documentation question, suggestion, or non-blocking defect | 5 business days |
Targets are response goals, not guaranteed resolution times. Incomplete severity or reproduction details may be reclassified.