What causes "unable to update license with ID: %s" in SigNoz/signoz?

Check the wrapped DB error (connection, constraint, undefined column) and fix accordingly

CodeInternal

CodeInternal

Error message

unable to update license with ID: %s

What it means

sqllicensingstore.Update failed to persist the storable license via bun's NewUpdate (WherePK + org filter); the DB error is wrapped as CodeInternal with the license ID.

Source

Thrown at ee/licensing/licensingstore/sqllicensingstore/store.go:77

		Scan(ctx)
	if err != nil {
		return nil, store.sqlstore.WrapNotFoundErrf(err, errors.CodeNotFound, "licenses for organizationID: %s does not exists", organizationID)
	}

	return storableLicenses, nil
}

func (store *store) Update(ctx context.Context, organizationID valuer.UUID, storableLicense *licensetypes.StorableLicense) error {
	_, err := store.
		sqlstore.
		BunDB().
		NewUpdate().
		Model(storableLicense).
		WherePK().
		Where("org_id = ?", organizationID).
		Exec(ctx)
	if err != nil {
		return errors.Wrapf(err, errors.TypeInternal, errors.CodeInternal, "unable to update license with ID: %s", storableLicense.ID)
	}

	return nil
}

View on GitHub (pinned to 5069bf80b0)

Solutions

Check the wrapped DB error (connection, constraint, undefined column) and fix accordingly
Run pending migrations so the licensing table schema matches the binary
Re-activate the license to re-create the row if it was deleted
Verify the organizationID in context matches the stored license's org_id

Defensive patterns

Strategy: try-catch

Try / catch

if err := store.Update(ctx, orgID, lic); err != nil {
	if errors.Ast(err, errors.CodeInternal) { log with storableLicense.ID; if no rows affected → fall back to Create }
}

Prevention

Run DB migrations with each SigNoz upgrade
Use upsert semantics for license persistence
Never delete license rows manually; use deactivate APIs

When it happens

Trigger: Refresh/Activate flows writing the license when the row's PK no longer exists, org_id doesn't match the WHERE clause, DB is down/schemaclass mismatch, or a constraint violation occurs on update.

Common situations: Stored license row deleted out-of-band so UPDATE matches 0 rows or errors; Postgres unavailable mid-request; migration not applied for new licensing columns; org context mismatch after re-provisioning the org.

Related errors

AI-assisted analysis of SigNoz/signoz@5069bf80b0 (2026-08-28). Data as JSON: /api/errors/c265866cea9a206a. Report an issue: GitHub.