payloadcms / payloadcms/payload
Join fields occasionally don't get populated properly
Open
Nobody has claimed this yet.
stale
status: needs-triage
- Dominant language
- TypeScript
- Stars
- 44.8k
- Forks
- 4.2k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 53
Description
Describe the Bug
When adding a join field the referenced collection item occasionally is not loaded properly on the overview.
Link to the code that reproduces this issue
https://github.com/khnn/test-project
Reproduction Steps
The reproduction is based on the blank template.
- Clone / install / start the dev server
- Seed via /seed?count=200
- Check on /admin/collections/posts?depth=1&limit=-1
Which area(s) are affected?
Not sure
Environment Info
I attached examples for Brave and Chrome, but this is also happening on FF and Safari.
Binaries:
Node: 22.21.1
npm: 10.9.4
Yarn: N/A
pnpm: 10.33.0
Relevant Packages:
payload: 3.81.0
next: 16.2.1
@payloadcms/db-sqlite: 3.81.0
@payloadcms/drizzle: 3.81.0
@payloadcms/graphql: 3.81.0
@payloadcms/next/utilities: 3.81.0
@payloadcms/richtext-lexical: 3.81.0
@payloadcms/translations: 3.81.0
@payloadcms/ui/shared: 3.81.0
react: 19.2.4
react-dom: 19.2.4
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 25.4.0: Thu Mar 19 19:30:44 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6000
Available memory (MB): 32768
Available CPU cores: 10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Run the linked test project, seed it with /seed?count=200, and reproduce the issue at /admin/collections/posts?depth=1&limit=-1 using the provided browser and package versions. Trace how join fields load referenced collection items on the posts overview; done means those items are consistently populated across the reported browsers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, react, typescript
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100