Before Submitting a Ticket
Check these resources first — many common questions are already answered:Documentation and FAQ
Browse the docs and search for the error code, model name, or feature you’re working with before opening a ticket.
Console Logs and Error Details
Check your application logs for the full error response. Note the
error.request_id, HTTP status code, error.code, and error.type — you’ll need these when filing a ticket.Submitting a Ticket
Open the Support Form
Click the Support button in the top-right corner of aiapi.fhddos.com to open the ticket submission form.
Include the Essential Details
Provide the following in every ticket to avoid back-and-forth delays:
| Detail | Where to find it |
|---|---|
| Timestamp of the issue | Your application logs or browser console |
| Request ID | error.request_id in the error body, or X-Oneapi-Request-Id response header |
| Expected vs. actual behavior | Describe what you intended to happen and what actually occurred |
| Reproduction steps | A minimal, step-by-step sequence that reliably triggers the issue |
Response Times and Priority
Response times and support priority levels are determined by your subscription plan. Upgrade your plan if you require guaranteed response-time SLAs or dedicated support access.For production incidents, clearly state the scope of impact and the urgency level in your ticket. This allows the support team to route your ticket to the appropriate priority queue and respond faster.
