How to debug "key not found: Tenant"

[buoyant pewter]

I'm running a multi-tenant Payload v3 app based on the official example.

Recently, I started seeing about 20 key not found: Tenant warnings in the browser console on every admin panel page load, plus an occasional single instance on the server (terminal).

Since Tenant appears many times in my codebase, I’m struggling to pinpoint the source. The browser console logs reference /_next/static/chunks/app/(payload)/admin/%5B%5B...segments%5D%5D/page.js, which is minified and unhelpful for debugging.

Any tips on narrowing this down, such as enabling more verbose logging to reveal the exact file/line?

[rocky nymph]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• The Payload Config - Config Location
• TypeScript - Overview
• Local API
• Migrations - When to run migrations - Postgres
• Custom Features - Server Feature - Feature load order

[dusky cypress]

I'm experiencing the same thing.

[buoyant pewter]

Okay, I created a fresh multi-tenant example from scratch via npx create-payload-app --example multi-tenant and key not found: Tenant is still being logged, so it's not my custom code trigerring it. I'll open a GitHub issue

https://github.com/payloadcms/payload/issues/11682

[short zealot]

I have the same issue. I think it is related to "tenantSelectorLabel" of multiTenantPlugin config.

[buoyant pewter]

Thanks to Jarrod for creating a PR that should address this and will likely be included in the next Payload release – https://github.com/payloadcms/payload/pull/11693