If a card displays “The content is corrupted,” some of its stored data no longer matches the format Heptabase currently expects. The content may still be recoverable, but preserve the original card while investigating.
Before trying a repair
Do not overwrite, restore, or delete the original card.
Version history only contains snapshots from the previous 60 days. Use it only when you can see a known-good version.
A Markdown export of a corrupted card may be blank. A new card created by AI Agent may also change special nodes, so do not treat either one as a lossless backup.
Try a safe test copy
Update Heptabase to the latest version, open the affected card, and add it to the AI conversation context. Ask AI Agent to create a separate test card without changing the original:
Do not modify, overwrite, restore, or delete the original card. Only read the original card and create a new test card that preserves as much of its content and special nodes as possible. Do not make any further changes to the original card.
Compare the new card with the original. Check tables, embeds, block mentions, placeholders, missing content, unexpected escaping, and any newly inserted content.
If the test copy is different
AI Agent supports many tables, embeds, block mentions, and other special nodes, but some special nodes cannot be reconstructed in a new card. The test card must not be treated as a lossless backup if any differences remain.
Keep both cards and contact support with the affected card link, your Heptabase version, and screenshots of the differences. Do not send raw card data unless support specifically asks for it and explains the recovery procedure.