payloadcms / payloadcms/payload
Collection features `orderable` and `enableQueryPresets` break admin panel on Cloudflare Workers
Open
@paulpopus is already working on this.
Since Jan 22, 2026.
area: ui
Bug
db: sqlite
plugin: db-d1-sqlite
- Dominant language
- TypeScript
- Stars
- 44.8k
- Forks
- 4.2k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 53
Description
Describe the Bug
When deploying Payload CMS to Cloudflare Workers (using D1 database), the following collection config options cause the admin panel to fail:
orderable: trueenableQueryPresets: true
The admin panel renders a blank white page for affected collections. API endpoints continue to work normally (return 200 OK with valid data).
Reproduction Steps
- Create a Payload CMS project configured for Cloudflare Workers + D1
- Add a collection with either
orderable: trueorenableQueryPresets: true - Deploy to Cloudflare Workers
- Navigate to the collection in the admin panel
- Observe blank white page instead of collection list
Expected Behavior
Collections with these options should render normally in the admin panel.
Workaround
Remove these options from collection configs when deploying to CF Workers:
export const MyCollection: CollectionConfig = {
slug: 'my-collection',
// orderable: true, // DISABLED: breaks CF Workers admin panel
// enableQueryPresets: true, // DISABLED: breaks CF Workers admin panel
// ... rest of config
}
Environment Info
Payload: 3.66.0
Next.js: 15.5.7
Runtime: Cloudflare Workers (OpenNext)
Database: Cloudflare D1 (SQLite)
Storage: Cloudflare R2
Which area(s) are affected?
- Admin UI
- Cloudflare Workers deployment
Additional Context
- The API endpoints work fine - this is specifically an admin panel rendering issue
- No errors appear in Cloudflare Workers observability logs
- The issue appears to be client-side React rendering failure
- Removing these options immediately fixes the issue
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.
Assessment
This issue has not been assessed yet.