Litera Contract Version Compare Triage

What this skill debugs

SpotDraft’s contract version comparison feature calls Litera Compare (hosted Compare Server + UI Compare flow). Failures often surface as:

• 422 from Litera with a generic “corrupt or unsupported format” message
• Browser/UI showing “This version of Litera Compare Online requires Litera Compare Server 9.5.3 or later” — this can appear even when the backend server is on a 9.24.x line; treat it as a symptom to verify server health and the real API error, not as proof of an old server version alone
• Compare works once, then breaks after swapping which version is “original” vs “modified” (customer may retry many times)
• UICompare path fails while non-UI Compare (e.g. RTF/DOCX output in Litera Swagger) succeeds for the same logical content
• Django logs WordServerError: "Word server raised an error when handling request", but the same compare later succeeds in production and neither Litera nor Word Server logs show a matching failure. Treat this as a possible misattributed / low-observability transient, not proof that Word Server was the real root cause.

Earliest failure point is usually: Litera rejecting one or both inputs (often PDF-related or conversion pipeline / Kofax), not SpotDraft’s generic “compare” button.

When to use / when not to use

Use when: