Skip to main content
All CollectionsQuick Start
Best Practices: Submit a Technical Support Request
Best Practices: Submit a Technical Support Request

This document provides guidance for submitting requests for technical support.

Updated over 2 months ago

If the problem is...

Help us troubleshoot by telling us…

Infrastructure

Timeouts, connection issues, deployment questions, etc.

  • Environment details (which flavor of K8S, e.g.)

  • GPUs/CPUs info

  • Which version of the product?

  • What are you trying to do?

  • Error codes and messages, if any?

Operational

Authentication issues, API problems, error codes, service failures, integration issues, etc.

  • SaaS or on-prem?

  • Which version of the product?

  • What were you trying to do when the problem happened?

  • API

    • Which endpoints were you using?

    • Can you share your query? Or at least provide the parameters you were sending?

    • If SaaS, when did you encounter the error?

  • Error codes and messages, if any

  • Are you able to reproduce the issue, or was it a once off?

A Scanner

Scanner performance, unexpected outcomes, fine-tuning support, etc.

  • SaaS or on-prem?

  • Which version of the product?

  • Which scanner and scanner version?

  • What are you trying to achieve?

  • Prompt dataset and expected results, if shareable

  • Logs

  • Model name & version, if applicable

The UI

Page not loading, formatting problems, UX issues, etc.

  • SaaS or on-prem?

  • Which version of the product? (The version number is in the bottom left of the navigation bar)

  • What were you trying to do when the problem happened?

  • UI screenshots showing the problem.

  • Console error messages, if any.

Documentation

Missing or incorrect documentation, etc.

  • Link to problematic help doc (if it exists)

  • Explanation of what’s missing or incorrect

Did this answer your question?