-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Open
Labels
Bugplugin: multi-tenant@payloadcms/plugin-multi-tenant@payloadcms/plugin-multi-tenantstatus: needs-triagePossible bug which hasn't been reproduced yetPossible bug which hasn't been reproduced yet
Description
Describe the Bug
When using multi-tenant plugin with some collections marked as global you are unable to delete the tenant. Attempting to do so leaves the delete request hanging without any errors in frontend or console.
Removing collections marked as global from the configuration fixes the issue, as well as setting cleanupAfterTenantDelete: false.
Link to the code that reproduces this issue
https://github.com/simovicaleksa/delete-tenant-reproduction
Reproduction Steps
- Clone the reproduction repo
docker compose up -dpnpm buildpnpm start- Create user with
super-adminrole - Create tenant
A - Publish
settingsglobal collection for tenantA(optional) - Try to delete tenant
A
Which area(s) are affected?
plugin: multi-tenant
Environment Info
Binaries:
Node: 24.10.0
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant Packages:
payload: 3.79.1
next: 15.4.11
@payloadcms/db-postgres: 3.79.1
@payloadcms/drizzle: 3.79.1
@payloadcms/graphql: 3.79.1
@payloadcms/next/utilities: 3.79.1
@payloadcms/plugin-multi-tenant: 3.79.1
@payloadcms/richtext-lexical: 3.79.1
@payloadcms/translations: 3.79.1
@payloadcms/ui/shared: 3.79.1
react: 19.2.1
react-dom: 19.2.1
Operating System:
Platform: win32
Arch: x64
Version: Windows 11 Pro
Available memory (MB): 32689
Available CPU cores: 16
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Bugplugin: multi-tenant@payloadcms/plugin-multi-tenant@payloadcms/plugin-multi-tenantstatus: needs-triagePossible bug which hasn't been reproduced yetPossible bug which hasn't been reproduced yet