https://sonarly.com/issue/3797?type=bug The `WorkflowHandleStaledRunsWorkspaceService.handleStaledRunsForWorkspace()` fetches all staled workflow runs without a limit and passes all IDs to a single `update()` call, which hits the ORM's hard 200-record update limit, preventing recovery of stuck workflow runs. Fix: Replaced the unbounded `find()` + single `update()` pattern with a batched do-while loop that processes staled workflow runs in chunks of `QUERY_MAX_RECORDS` (200). **What changed:** - Added `import { QUERY_MAX_RECORDS } from 'twenty-shared/constants'` (same import used by sibling `workflow-run-enqueue.workspace-service.ts`) - Changed the `find()` call to include `select: { id: true }` and `take: QUERY_MAX_RECORDS` to limit each batch to 200 records - Wrapped the find+update in a `do-while` loop that continues fetching and updating batches until fewer than `QUERY_MAX_RECORDS` are returned (meaning all staled runs have been processed) - Added a guard so `recomputeWorkflowRunNotStartedCount` is only called if at least one record was updated **Why this works:** Each batch updates at most 200 records, staying within the `WorkspaceUpdateQueryBuilder`'s `QUERY_MAX_RECORDS` limit. After each batch is updated (status changed from `ENQUEUED` → `NOT_STARTED`), those records no longer match `getStaledRunsFindOptions()`, so the next `find()` naturally returns the next set of staled runs. This is the same pattern used by `workflow-run-enqueue.workspace-service.ts` (lines 83-98) which already works correctly in production.
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · Roadmap ·
Discord ·
Figma
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
- Customize your objects and fields
- Create and manage permissions with custom roles
- Automate workflow with triggers and actions
- Emails, calendar events, files, and more
Personalize layouts with filters, sort, group by, kanban and table views
Customize your objects and fields
Create and manage permissions with custom roles
Automate workflow with triggers and actions
Emails, calendar events, files, and more
Stack
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Jotai, Linaria and Lingui
Thanks
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
- Star the repo
- Subscribe to releases (watch -> custom -> releases)
- Follow us on Twitter or LinkedIn
- Join our Discord
- Improve translations on Crowdin
- Contributions are, of course, most welcome!




