openclaw - 💡(How to fix) Fix conversation_messages table missing parent_message_id column (gateway crashes on every message) [1 participants]

Error (OperationalError): (sqlite3.OperationalError) table conversation_messages has no column named parent_message_id

• Fresh volume (no prior state) — same error
• Disabling all plugins individually — same error
• Removing manifest extension entirely — same error
• Running openclaw doctor --fix — same error
• Different OpenClaw versions (2026.4.2, 2026.4.5) — same error
• Different streaming, replyToMode, tools.profile, tools.exec.ask configs — same error

TL;DR

The most likely fix is to update the conversation_messages table schema to include the parent_message_id column.

Guidance

• Verify that the conversation_messages table is being generated correctly by TypeORM, and that the parent_message_id column is defined in the corresponding entity class.
• Check the entity class for the conversation_messages table to ensure that the parent_message_id property is properly decorated with TypeORM metadata.
• Review the database migration scripts to ensure that the parent_message_id column is being added to the conversation_messages table.
• If using a custom database schema, verify that the parent_message_id column is included in the schema definition.

Example

// Example entity class for conversation_messages table
import { Entity, Column, PrimaryColumn } from 'typeorm';

@Entity()
export class ConversationMessage {
  @PrimaryColumn()
  id: number;

  @Column()
  channel_id: number;

  @Column()
  role: string;

  @Column()
  content: string;

  @Column()
  parent_message_id: number; // Ensure this property is defined and decorated
}

Notes

The issue may be related to a mismatch between the entity class definition and the database schema. Ensuring that the parent_message_id column is properly defined in the entity class and included in the database schema should resolve the issue.

Recommendation

Apply a workaround by manually adding the parent_message_id column to the conversation_messages table schema, or update the entity class to include the parent_message_id property with proper TypeORM metadata. This should resolve the OperationalError and allow messages to be processed normally.