Skip to content

Every notetaker transcribe/summarize enqueue fails: "ON CONFLICT clause does not match any PRIMARY KEY or UNIQUE constraint" #184

Closed

Description

@MohammadHadi2031

Before submitting

  • I've searched existing issues and this isn't a duplicate.
  • This is a reproducible bug in Calnode — not a configuration/setup question or a feature request.

What's the bug?

Migration 00065 replaced UNIQUE(type, payload) on jobs with the partial index ux_jobs_type_payload_live … WHERE status IN ('pending','running'). SQLite only accepts a partial index as an upsert target when the ON CONFLICT clause repeats its WHERE. enqueueJob (internal/handler/notetaker.go) still uses a bare ON CONFLICT(type, payload), so since 00065 the statement fails to prepare:

SQL logic error: ON CONFLICT clause does not match any PRIMARY KEY or UNIQUE constraint (1)

No notetaker job can be queued. No test covers enqueueJob. The old DO UPDATE would also have reset a running job to pending, so it would run twice.

Steps to reproduce

NA

Calnode version / commit

v0.11.2

How are you running Calnode?

Self-hosted — Docker

Logs, screenshots, or anything else

No response

Activity

  1. pullfrog commented on Oct 28, 2026

    @pullfrog
    Contributor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions