Sonarly Claude Code
03db2b1837
https://sonarly.com/issue/19081?type=bug Transient network failures (TCP-level "fetch failed") when calling Microsoft Graph API during calendar event import are misclassified as UNKNOWN errors, causing the calendar channel to be permanently marked as failed instead of being retried. Fix: The root cause is that `parseMicrosoftCalendarError` only switches on HTTP `statusCode`. When Node.js undici throws `TypeError: fetch failed` (a TCP-level network failure), there is no `statusCode` — the error falls to `default` and is classified as UNKNOWN. This triggers `handleUnknownException`, which permanently marks the calendar channel as FAILED_UNKNOWN and flushes all pending events — an unrecoverable state for a transient network blip. Changes made: 1. **parse-microsoft-calendar-error.util.ts** (primary fix): - Added `isNetworkError()` helper that detects TypeError instances (undici fetch failures) and errors with `cause.code` matching known network error codes (ECONNRESET, ENOTFOUND, ETIMEDOUT, ECONNABORTED, ECONNREFUSED, EHOSTUNREACH, ERR_NETWORK, UND_ERR_CONNECT_TIMEOUT, UND_ERR_SOCKET). - Network errors are now classified as TEMPORARY_ERROR → retry with backoff instead of permanent failure. - Added safety-net guard: errors with no `statusCode` that aren't detected as network errors also get TEMPORARY_ERROR (fail-safe toward retry). - Reclassified HTTP 500/502/503/504 from UNKNOWN to TEMPORARY_ERROR, matching the messaging-side pattern. 2. **parse-microsoft-messages-import.util.ts** (proactive fix): - Added the same `isNetworkError()` guard before HTTP status code checks, preventing the identical bug from manifesting in Microsoft message import.
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!