Skip to Content
ReferenceTroubleshooting

Troubleshooting

Start with the learner-visible symptom, then verify the earliest failed boundary in the flow: host launch, role-play loading, voice connection, transcript, or evaluation.

Generic error screen with Try again action

Common issues

SymptomLikely causeRecommended action
Missing-parameter errorIframe URL has no non-empty rolePlayIdCorrect the launch URL and reload the iframe
No-token errorParent omitted syntphony_V2V_token_submitted or its tokenWait for client-ready, validate the message shape, and send from the approved origin
Expired-token errorRefresh was empty, rejected, or took more than ten secondsImplement the refresh round trip and return a current token promptly
Role-play remains unavailableID is wrong/inactive, SCAI agent is missing/inactive, session data is invalid, or authorization failedVerify the active role-play/agent relationship and inspect the role-play GET status
Briefing remains in loading stateNo usable localized briefing content reached the clientVerify locale content and the role-play response
Microphone errorBrowser denial, missing iframe permission, insecure origin, or device policyGrant microphone permission, add iframe allow="microphone", use HTTPS, and check device policy
Call never activatesSCAI credential, environment, DNIS, WebSocket, SDP, or media-path failureInspect the credential and signalling sequence; validate SCAI readiness and network access
Call drops repeatedlyICE/WebSocket recovery is exhausted or the network/SCAI service is unstableCheck proxy, firewall, NAT/TURN, and SCAI availability; start a new attempt after recovery fails
Transcript is missing or inaccurateUnsupported metadata, no-input recognition, or speech-recognition qualityCheck SCAI metadata and audio quality; do not treat the transcript as a guaranteed verbatim record
Feedback-analysis errorNo transcript turns, invalid locale/request, authentication failure, AI Factory error, or invalid evaluation outputInspect the evaluation status and ProblemDetails; verify criteria and response validation
Recommended courses are absentEvaluation returned an empty list; current core schema does not request coursesTreat courses as optional or extend and validate the evaluation design
Download opens a print dialogCurrent export uses browser printingPrint or select Save as PDF
Host shows no completionCompletion was not configured, claims were missing, or background delivery failedVerify target platform, upn, cmid, completion queue, retries, and LPI response
Analytics has no attemptTenant/runtime missing or token/session creation failedVerify analytics enablement and session creation; do not infer learner failure from missing telemetry

Microphone checklist

  1. Load both host and iframe over HTTPS.
  2. Include allow="microphone" on the iframe.
  3. Grant site permission in the browser.
  4. Select the correct operating-system input and output devices.
  5. Close applications holding exclusive microphone access.
  6. Check browser, device-management, and corporate privacy policies.

Microphone access blocked screen showing permission instructions for browser and iframe

Network checklist

The learner’s browser must reach:

  • The SCL static application.
  • Evaluation and Integration Credentials APIs over HTTPS.
  • The configured SCAI WebSocket endpoint.
  • The WebRTC media path, including any required TURN infrastructure.
  • The Role Play Evaluation API analytics proxy when analytics is enabled.

VPNs, TLS inspection, proxies, content filters, restrictive NAT, and firewall policy can affect signalling and media differently. A successful HTTPS page load does not prove that WebSocket or WebRTC is allowed.

Evaluation checklist

  1. Confirm the transcript contains at least one valid turn.
  2. Confirm elapsedTimeSeconds is present and non-negative.
  3. Confirm Accept-Language uses xx-XX form.
  4. Confirm the role-play and its SCAI agent remain active.
  5. Confirm evaluation criteria exist and match the expected speaker mapping.
  6. Use the response status to distinguish validation (400), identity (401), not found (404), invalid AI output (422), and dependency failure (502).
  7. Do not automatically replay an evaluation request until duplicate completion/analytics effects have been assessed.

Safe support information

Provide:

  • Environment and approximate timestamp.
  • Role-play ID and analytics session ID, if visible to authorized operators.
  • Browser/version, operating system, device type, and network context.
  • Learner-visible error category.
  • Sanitized request status, correlation identifier, and dependency state.

Never provide bearer or technical tokens, APIM keys, learner identifiers, transcript text, raw voice, or unsanitized request/response bodies.