KamoCRM

Don't fetch org with a precision-truncated id

Fixkamo-internal
Shipped
1 ஜூலை, 2026 அன்று 8:28 AM UTC
Author
kamo
Commit
1f065da

LabelManager derived orgIdStr from getOrgIdString() (precision-safe) with a fallback to String(organization.id). organization.id is a JS number and silently truncates CockroachDB int64 ids past MAX_SAFE_INTEGER (...822 → ...800). On first render, before userInfo loads, the fallback fired the applied-model and org-GET calls with the wrong id, which 404 and surfaced as 'Failed to load settings'. Only use the numeric fallback when the id is a safe integer; otherwise wait for the precision-safe id.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing