OpenMAIC

This is a known bug in OpenMAIC v1.1.2. When you add a custom keyless provider (requiresApiKey: false, e.g. a local OpenAI-compatible TTS endpoint), addCustomTTSProvider in lib/store/settings.ts saves the endpoint only to customDefaultBaseUrl and leaves baseUrl: ''. On reload, the validation isProviderUsable in lib/store/settings-validation.ts runs if (cfg.requiresApiKey === false) return !!cfg.baseUrl;, marks the provider as unusable, and silently falls back to browser-native-tts. Since dubbing UI (per-line preview/regenerate buttons, 'regenerate all dubbing', voiced chips) is gated on ttsProviderId !== 'browser-native-tts', all dubbing controls vanish.

Fix (verified): in lib/store/settings.ts, write the URL to both fields when adding/updating a custom provider:

addCustomTTSProvider: (id, name, baseUrl, requiresApiKey, defaultModel) =>
  set((state) => ({
    ttsProvidersConfig: { ...state.ttsProvidersConfig, [id]: {
      ...,
      baseUrl,                  // was ''
      customDefaultBaseUrl: baseUrl,
      ...
    }},
    ttsProviderId: id,
  })),

Alternative fix: in isProviderUsable, accept customDefaultBaseUrl as a fallback for custom-* provider ids, e.g. return !!(cfg.baseUrl || cfg.customDefaultBaseUrl); for the keyless branch. Apply the same change to custom ASR providers, then rebuild (pnpm build && pnpm start). Temporary workaround without code changes: re-select the custom provider in Settings → Model Services → TTS after each reload (it works until the next reload), or delete and re-add the provider each session.

This is a known bug in OpenMAIC 1.2.0-rc.2. The PBL v3 studentFeedback gate (lib/server/pbl-v3/guided-review.ts, lines 71-79) used a literal substring match against the latest student message, so any feedback the agent wrapped or summarized (e.g. Student reply: "...") failed the check and blocked progression via read_next_skill or complete_stage. Fix: upgrade to a build that includes PR #1963 (commit 4de9467d, merged into the integration/shared-sandbox branch). The fix accepts quoted or summarized feedback and answers spread across multiple learner messages, while still enforcing real-reply, stage, and artifact-version checks.

This happens because postProcessInteractiveHtml (in packages/@openmaic/generation/src/interactive-post-processor.ts) skips injecting the KaTeX auto-render script and MutationObserver whenever the generated HTML already contains the string katex. When the model-generated page ships its own katex.min.js/katex.min.css (common), auto-rendering is never installed, so \(...\) and $...$ print literally. In sandboxed about:srcdoc iframes, the page's own renderMathInElement() call also fails with Uncaught ReferenceError: renderMathInElement is not defined because external CDN scripts cannot load. Two failure modes: (1) math never renders when the page includes KaTeX core; (2) labels filled by the page's own init() stay raw on first paint because the observer is installed after the initial render pass. Fix (PR #1606): guard injection on auto-render/renderMathInElement instead of the bare katex string; when KaTeX core is already present, inject only the missing auto-render contrib script and the MutationObserver; after installing the observer, run one extra render pass after a ~300ms settle timeout and again on window load so init()-filled labels render on first paint.

This error occurs when PBL v3 background polling and a teaching tool (e.g., read_next_skill, request_skill_review, complete_stage) call touchEnvironment for the same study concurrently, so the second renewal fails to acquire the environment advisory lock and returns 409 before recording its result. **Workaround:** retry the teaching action after the other operation finishes — the retry typically succeeds. **Permanent fix:** upgrade to a build including PR #1964 (merge commit 3446978c on integration/shared-sandbox), which rereads the durable renewal timestamp and retries explicit environment-lock contention within a five-second budget without replaying teaching actions. Note this fix landed after v1.2.0-rc.2 and may not yet be merged into main.

A material fails with 'Parsing service unavailable' when no parser is configured. An administrator must first configure a parser for the knowledge base, then open the knowledge base page and use 'Parse again' on the failed material to retry. For media that fail because they are too long, check the duration limit shown in the failure reason. Note that conversation-sourced materials have no 'Parse again' row action — manage and re-parse them directly from the knowledge base page. Clearer reason-specific failure guidance, localized business error messages (previously English-only), and corrected singular/plural wording ('1 material' instead of '1 materials') were shipped in PR #1923, merged as commit 84a88bc4.