Crosstalk-Solutions/project-nomad · error · Error

Failed to delete chat session

Error message

Failed to delete chat session

What it means

ChatService.deleteSession rethrows this after logging when findOrFail(sessionId) fails (already deleted / bad id) or when cascading deletion of the session row fails at the DB level. Because the not-found path and the DB-failure path share one catch, both look identical to the caller.

Source

Thrown at admin/app/services/chat_service.ts:226

          error instanceof Error ? error.message : error
        }`
      )
      throw new Error('Failed to add message')
    }
  }

  async deleteSession(sessionId: number) {
    try {
      const session = await ChatSession.findOrFail(sessionId)
      await session.delete()
      return { success: true }
    } catch (error) {
      logger.error(
        `[ChatService] Failed to delete session ${sessionId}: ${
          error instanceof Error ? error.message : error
        }`
      )
      throw new Error('Failed to delete chat session')
    }
  }

  async getMessageCount(sessionId: number): Promise<number> {
    try {
      const count = await ChatMessage.query().where('session_id', sessionId).count('* as total')
      return Number(count[0].$extras.total)
    } catch (error) {
      logger.error(
        `[ChatService] Failed to get message count for session ${sessionId}: ${error instanceof Error ? error.message : error}`
      )
      return 0
    }
  }

  async generateTitle(sessionId: number, userMessage: string, assistantMessage: string, model: string) {
    try {
      let title: string

View on GitHub (pinned to 0bd1c6f4f9)

Solutions

1. Check logs for '[ChatService] Failed to delete session <id>: <cause>'
2. If it's a double-delete, make delete idempotent: use ChatSession.query().where('id', sessionId).delete() or treat E_ROW_NOT_FOUND as success
3. Verify FK constraints on chat_messages use ON DELETE CASCADE (or delete messages first)
4. Fix DB connectivity if the delete itself is failing

Example fix

// before
const session = await ChatSession.findOrFail(sessionId)
await session.delete()

// after
const session = await ChatSession.find(sessionId)
if (!session) return // already deleted — idempotent
await session.delete()

if (!(await ChatSession.find(sessionId))) return // idempotent delete — nothing to do

async function isSessionDeletable(id: number): Promise<boolean> {
  return (await ChatSession.find(id)) !== null
}

try { await chat.deleteSession(id) } catch (e) { if (e.message === 'Failed to delete chat session' && !(await ChatSession.find(id))) return /* already gone */ throw e }

When it happens

Trigger: Deleting a session id that no longer exists (double delete, stale UI), or a DB error during the delete transaction (connection loss, FK restriction preventing removal).

Common situations: User double-clicks delete or two tabs delete the same session; a schema where chat_messages has ON DELETE RESTRICT so the session row can't be removed while messages exist.

Related errors

• Failed to update chat session
• Failed to create chat session
• Failed to add message
• Failed to delete all chat sessions
• No response from Ollama

AI-assisted analysis of Crosstalk-Solutions/project-nomad@0bd1c6f4f9 (2026-08-27). Data as JSON: /api/errors/e23ebbe7b4fd5eb2. Report an issue: GitHub.