Sonarly Claude Code
68c252fc24
https://sonarly.com/issue/36163?type=bug Creating a new workspace fails with an unhandled exception when no instance-command upgrade migration row exists in the database — a state that occurs on every fresh Twenty installation before any upgrade commands have been run. Fix: ## What changed and why ### Root cause `WorkspaceService.activateAndInitializeUpgradeState` called `getLastAttemptedInstanceCommandOrThrow()`, which throws `'No instance command found — the database may not have been initialized'` when the `upgradeMigration` table has no global instance-command rows. On a fresh installation no instance commands have ever been run, so the table is empty, and every workspace activation attempt fails — leaving the workspace permanently stuck in `ONGOING_CREATION`. ### Fix (3 files + 1 test) **`upgrade-sequence-reader.service.ts`** — `getInitialCursorForNewWorkspace` now accepts `null` as its argument. When `null` is received (fresh install, no migration history), it falls back to the last workspace command in the sequence and marks it `completed` — identical to the pre-cross-version-upgrade behaviour of the removed `getLastWorkspaceCommand()` helper. This is the correct semantic: a brand-new workspace has no pending workspace commands to run. **`workspace.service.ts`** — `activateAndInitializeUpgradeState` now calls the non-throwing `getLastAttemptedInstanceCommand()` (returns `null` on an empty table) instead of `getLastAttemptedInstanceCommandOrThrow()`. **`dev-seeder.service.ts`** — both `seedDev` and `seedEmptyWorkspace` apply the same fix for consistency; they share the same bug on fresh dev environments. **`upgrade-sequence-reader.service.spec.ts`** — adds a test that passes `null` and asserts the last workspace command in the sequence is returned as the initial cursor.
The #1 Open-Source CRM
Website · 
Documentation · 
Roadmap · 
Discord · 
Figma
Why Twenty
Twenty gives technical teams the building blocks for a custom CRM that meets complex business needs and quickly adapts as the business evolves. Twenty is the CRM you build, ship, and version like the rest of your stack.
Learn more about why we built Twenty
Installation
Cloud
The fastest way to get started. Sign up at twenty.com and spin up a workspace in under a minute, with no infrastructure to manage and always up to date.
Build an app
Scaffold a new app with the Twenty CLI:
npx create-twenty-app my-app
Define objects, fields, and views as code:
import { defineObject, FieldType } from 'twenty-sdk/define';
export default defineObject({
nameSingular: 'deal',
namePlural: 'deals',
labelSingular: 'Deal',
labelPlural: 'Deals',
fields: [
{ name: 'name', label: 'Name', type: FieldType.TEXT },
{ name: 'amount', label: 'Amount', type: FieldType.CURRENCY },
{ name: 'closeDate', label: 'Close Date', type: FieldType.DATE_TIME },
],
});
Then ship it to your workspace:
npx twenty deploy
See the app development guide for objects, views, agents, and logic functions.
Self-hosting
Run Twenty on your own infrastructure with Docker Compose, or contribute locally via the local setup guide.
Everything you need
Twenty gives you the building blocks of a modern CRM (objects, views, workflows, and agents) and lets you extend them as code. Here's a tour of what's in the box.
Want to go deeper? Read the 
User Guide for product walkthroughs, or the Documentation for developer reference.
|
|
|
|
|
|
Learn more about version control in docStack
TypeScript
Nx
NestJS, with BullMQ, 
PostgreSQL, 
Redis
React, with Jotai, Linaria and Lingui
Thanks
Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
Star the repo · Discord · 
Feature requests · Releases · 
X · 
LinkedIn · 
Crowdin · 
Contribute