Setting the file. One moment.
Common Issues · Zoom Cobrowse SDK · anthropics/knowledge-work-plugins · Skills Docs
Quick diagnostics for Zoom CoBrowse SDK issues.
Ensure SDK script/package is loaded.
Verify role-specific JWT generation on server.
Validate token expiry and clock skew.
Confirm session PIN flow between customer and agent.
ContentsBack to the top of the page 22
Validate Data
Tech Debt
62
Recruiting Pipeline
71
Vendor Check
125
Zoom Meeting SDK Web
88
Vendor Review
181
Create An Asset
Video Sdk/web
Symptom : Official doc links you found are stale or return 404.
Prefer the curated references under references/ (these are meant to stay stable even if external URLs drift).
If you need working code, start from official sample repos referenced by the skill, then adapt to your stack.
Symptom : You built an “agent creates session” endpoint, but the customer flow seems to actually start the share / generate the PIN.
Treat customer start/share as the action that creates the shareable context (PIN/session), then the agent joins using that PIN/session info.
Keep your server responsibilities narrow: token minting, optional auditing, and routing; avoid inventing “session creation” semantics that the SDK already owns.
Symptom : UI shows one PIN from backend/session record and another PIN from SDK event, agent gets Pin not found or Cobrowse code not found.
Treat session.on("pincode_updated") as the authoritative support PIN for agent entry.
Display exactly one primary PIN in UI (label it clearly as “Support PIN”).
Do not surface provisional/debug PINs to users.
When opening agent page with ?pin=..., prefer freshly generated links and avoid stale bookmarks.
Symptom : Zoom-hosted agent desk shows:
Cobrowse code not found
error code 30308
Ensure customer session is active and not expired before agent joins.
Use the latest PIN emitted by pincode_updated.
If your app restarts or uses in-memory state, persist session/PIN mapping or avoid strict local PIN gating for desk launch.
Have agent re-enter a fresh PIN from a newly started customer session.
Symptom : Quickstarts assume Vite/modern build pipeline; your plain HTML/Express adaptation breaks.
Load the SDK exactly as the official snippet expects (script order matters).
Avoid bundler-only patterns in plain HTML (ESM imports, import.meta, etc.) unless you add a bundler.
troubleshooting/common-issues.md