QAVE Studio Docs
QAVE Studio Docs
Sign inGet started — the Studio loop
Getting StartedFirst assurance runQuick assure
ConceptsLifecycleGlossaryHow QAVE Studio worksComing soon
Account & workspaceSignup and loginPeopleDemo creditsRolesSettings
Generate simulation suitesContext templatePII and field enhanceDimensionsAgents and plannerDraft review and Save
ExportExport formatsExport formats (detail)
Assurance SDKSDK overviewQAVE Studio suite fetch APIAgent and JSONL queueLangfuse bridge
Execute and tracesRecipe chatbot (reference SUT)TracingFetch tracing
AssureEvaluate APIRubrics and evidenceReading scores
History
WorkbenchGolden data
CoverageCoverage dashboardCoverage strategiesCoverage advisorTest case quality
RAG AssuranceRAG runsRAG datasetsRAG analytics
Project evalsError analysisUnderstanding scores
Studio guidesDimensionsTuplesConversation modesMulti-lingual testingWorkflowsHuman reviewBest practices
ReferenceAPI and packagesTroubleshooting
Reference

Troubleshooting

Common customer-facing issues across Studio, generation, SDK, and assure.

I cannot open Documentation without logging in

/documentation on the app redirects to the public docs site at docs.<your domain>. That site does not require a login. If you are sent to login instead, contact support — the auth allowlist may be misconfigured.

Signup email never arrives

  1. Check spam for the verification message.
  2. Use the copy-code / verify screen if the product shows a code.
  3. Wait a minute and retry; mail providers can delay delivery.

Login fails with correct password

Use the main Sign in form with your organisation email and password. Do not use Staff sign-in unless your Qapitol contact told you to.

Demo credits request is blocked

Only one credit request can be pending. Wait for approval or rejection, then try again. See Demo credits.

Export empty / suite missing

Suites must be APPROVED. Save from Generation already approves; older drafts need approval first. See Export.

Assure returns 401

SDK or API keys must match the project. Rotate keys under Settings and update your client.

SDK agent never scores the real chatbot

The recipe-chatbot reference SUT has no MCP evaluate tool. Use HTTP chat + Langfuse/paste for real scoring, or mock MCP for demos only. See Execute.

Scores look wrong

  • Confirm messages/trace shape matches the normalizer
  • Confirm Criterion / rubric selection
  • Spot-check evidence for / against against human judgment
  • See Reading scores and Understanding scores

History empty

Ensure evaluate completed and you are on the correct project. Check History filters if results seem missing.

Coverage looks stuck or misleading

If the coverage banner is amber (in flight), wait for the pipeline stage to finish before trusting readiness. See Coverage dashboard.

Error Analysis will not submit

You need at least three Fail or Unsure annotations with observations. Unannotated rows are skipped. See Error analysis.

API and packages

Quick index of real package and route names used in code samples.

On this page

I cannot open Documentation without logging inSignup email never arrivesLogin fails with correct passwordDemo credits request is blockedExport empty / suite missingAssure returns 401SDK agent never scores the real chatbotScores look wrongHistory emptyCoverage looks stuck or misleadingError Analysis will not submit