Elgato_dark/twenty
1
0
Fork 0
mirror of https://github.com/twentyhq/twenty synced 2026-04-21 13:37:22 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 17
Building a modern alternative to Salesforce, powered by the community.
11533 commits 554 branches 416 tags 1.7 GiB
TypeScript 78.6%
MDX 17.7%
JavaScript 3.2%
Python 0.3%
Find a file
Sonarly Claude Code 2181fb541e fix: handle deleted UserWorkspace in contact creation and connected account cleanup 
https://sonarly.com/issue/26526?type=bug

When a user is removed from a workspace (via workspace-member deletion or user removal), the
    UserWorkspace row is hard-deleted synchronously, but the associated ConnectedAccount rows are
    only cleaned up asynchronously via a BullMQ job (DeleteWorkspaceMemberConnectedAccountsCleanupJob).
    That cleanup job has a bug: it queries for the workspace member without `withDeleted: true`,
    finds nothing (the member is already soft-deleted), and silently returns — never deleting the
    connected accounts. The orphaned connected accounts continue syncing email, and when new
    contacts are discovered, the CreateCompanyAndContactJob tries to look up the now-deleted
    UserWorkspace by its stale `userWorkspaceId`, throwing:
      `Error: UserWorkspace with id efe7fd46-238b-464f-b3a4-19c72c4f0141 not found`

    This failure path was introduced by commit d3f0162cf5 (2026-04-06, "Remove connected account
    feature flag"), which changed ConnectedAccount from a workspace entity (with a direct
    `accountOwnerId` → WorkspaceMember relation) to a core entity (with a `userWorkspaceId` UUID
    column and no foreign key to UserWorkspace). The old code looked up the account owner directly;
    the new code adds an intermediate UserWorkspace lookup that breaks when the row is gone.

Fix: Two changes that work together to fix the crash:

1. **create-company-and-contact.service.ts** (proximate fix): When UserWorkspace is not found, return `null` instead of throwing. The downstream `createCompaniesAndPeople()` already accepts `accountOwner: WorkspaceMemberWorkspaceEntity | null` and handles it gracefully — contacts are still created, just without a `createdBy.workspaceMemberId`. This stops the Sentry error immediately.

2. **delete-workspace-member-connected-accounts.job.ts** (root cause fix): Three changes:
   - Added `withDeleted: true` to the workspace member query so soft-deleted members are still found
   - Added `shouldBypassPermissionChecks: true` to the repository (consistent with other system jobs)
   - Added fallback path: when UserWorkspace is already hard-deleted, scan for orphaned connected accounts in the workspace (accounts whose `userWorkspaceId` references a non-existent UserWorkspace row) and delete them

Together: the cleanup job now actually cleans up connected accounts when a member is removed, AND the contact creation service no longer crashes if an orphaned account still manages to trigger a sync.
2026-04-15 09:07:51 +00:00
.claude-pr Upgrade command internal doc (#19541) 2026-04-10 09:43:06 +00:00
.cursor Rename standard and custom apps (#19631) 2026-04-13 13:13:59 +00:00
.github Deprecate IS_RECORD_TABLE_WIDGET_ENABLED feature flag (#19662) 2026-04-13 21:13:15 +00:00
.vscode Migrate from ESLint to OxLint (#18443) 2026-03-06 01:03:50 +01:00
.yarn Refactor dependency graph for SDK, client-sdk and create-app (#18963) 2026-03-26 10:56:52 +00:00
packages fix: handle deleted UserWorkspace in contact creation and connected account cleanup 2026-04-15 09:07:51 +00:00
.dockerignore Scaffold light twenty app dev container (#18734) 2026-03-18 20:10:54 +01:00
.gitattributes Consolidate Prettier config and improve consistency (#15191) 2025-10-18 12:24:35 +02:00
.gitignore halftone v2 (#19573) 2026-04-11 10:00:24 +00:00
.mcp.json Fix AI chat re-renders and refactored code (#18585) 2026-03-21 12:52:21 +00:00
.nvmrc Upgrade to Node 24 (#13730) 2025-08-07 17:02:12 +02:00
.yarnrc.yml Refactor dependency graph for SDK, client-sdk and create-app (#18963) 2026-03-26 10:56:52 +00:00
CLAUDE.md Upgrade command internal doc (#19541) 2026-04-10 09:43:06 +00:00
jest.preset.js Move tools/eslint-rules to packages/twenty-eslint-rules (#17203) 2026-01-17 07:37:17 +01:00
LICENSE feat(sso): allow to use OIDC and SAML (#7246) 2024-10-21 20:07:08 +02:00
nx.json fix: replace npm pkg set with node script in set-local-version target (#19344) 2026-04-05 18:56:37 +00:00
package.json Bump @storybook/react-vite from 10.2.13 to 10.3.3 (#19232) 2026-04-02 08:49:11 +00:00
README.md docs: fix contributor docs links and typos (#18637) 2026-03-14 12:54:31 +01:00
tsconfig.base.json Revert "[hacktoberfest] feat: add fireflies" (#15589) 2025-11-04 12:25:23 +01:00
yarn.config.cjs [ENHC] Create Yarn constraints to validate node version (#10542) 2025-02-27 15:18:07 +01:00
yarn.lock Fix testimonials background, faq clickability and some case-studies page edits. (#19657) 2026-04-13 21:19:41 +00:00

README.md

Twenty logo

The #1 Open-Source CRM

🌐 Website · 📚 Documentation · Roadmap · Discord · Figma


Cover


Installation

See: 🚀 Self-hosting 🖥️ Local Setup

Why Twenty

We built Twenty for three reasons:

CRMs are too expensive, and users are trapped. Companies use locked-in customer data to hike prices. It shouldn't be that way.

A fresh start is required to build a better experience. We can learn from past mistakes and craft a cohesive experience inspired by new UX patterns from tools like Notion, Airtable or Linear.

We believe in open-source and community. Hundreds of developers are already building Twenty together. Once we have plugin capabilities, a whole ecosystem will grow around it.


What You Can Do With Twenty

Please feel free to flag any specific needs you have by creating an issue.

Below are a few features we have implemented to date:

Personalize layouts with filters, sort, group by, kanban and table views

Companies Kanban Views

Customize your objects and fields

Setting Custom Objects

Create and manage permissions with custom roles

Permissions

Automate workflow with triggers and actions

Workflows

Emails, calendar events, files, and more

Other Features


Stack

Thanks

Chromatic Greptile Sentry Crowdin E2B

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