If a card displays "The content is corrupted.", its underlying data no longer matches the format Heptabase expects. The content is usually still recoverable, and you can repair the card yourself with AI Agent mode.
Why a card's content becomes corrupted
This happens when some of the card's data was saved in a format that doesn't match Heptabase's schema. The most common sources are:
Editing the card through the Heptabase CLI
Editing the card through an MCP integration
Copying and pasting content directly into the card
For example, a due-date field expects a calendar date but receives a specific time, or a color field accepts only Heptabase's preset values but receives one outside that set. If you've edited the affected card through any of these, that's the most likely cause.
Repair the card with AI Agent mode
AI Agent mode can read the card's data and rewrite the invalid parts so the card matches the current schema.
Note: Agent mode uses AI credits. If you don't have credits available to run it, contact support for help.
Open the card showing the error.
Open the AI chat and switch to Agent mode.
Select the GPT 5.5 model. We recommend a more capable model for this, but you can also use one you're familiar with.
Confirm the affected card is open and in the chat's context, then send the repair request below.
Example:
This card has a data format (schema) problem. Please investigate it and try to fix the card so its data matches Heptabase's current schema.
Once the Agent finishes, it rewrites the fields that don't fit the schema, and the card's content should display again.
If the error returns
If the message comes back right after a specific action, such as editing the same card again through the CLI, an MCP tool, or another paste, stop that action. It is likely re-introducing the invalid format at the source.
If Agent mode cannot repair the card, or the content is still missing afterward, contact support with the card's details and a screenshot.