Topic Links 22 Archive Fix Patched Guide

Restoring the Past: How the "Topic Links 22" Archive Fix Patched Legacy Connections

Metadata Mismatch

: The archival header did not match the underlying content ID, causing the system to reject the connection as "unauthenticated" or "missing." 3. Implementation of the Fix topic links 22 archive fix patched

1. Archive index drift — the archive index format changed (ID format and timestamp encoding) between TL21→TL22, and link generator continued producing legacy-format archive keys.
2. Link-hash mismatch — link hashing used a different normalization (whitespace, Unicode normalization, or case handling) when link records were created vs. when archives were queried, causing lookup failures.
3. Redirect-race / cache TTL misalignment — front-end caches kept stale redirect records pointing to removed ephemeral archive endpoints.
4. Metadata mismatch — archived items’ metadata (canonical slug, published_at) were stored differently (UTC vs. local, plus missing canonical flag) so UI logic misclassified archived links as “draft” or “missing.”
5. Partial rollouts — an A/B rollout left some nodes on old logic, creating inconsistent behavior across requests.

• Unit tests: