- Shipped
- 26 Agosti 2026, 07:34 UTC
- Author
- Kamo
- Commit
- f7bf928
The caller cannot work this out and must stop trying. GET /org/{id} answers with the entity, whose `domains` is LAZY and serializes as null outside a transaction — so a client deriving the domain from it falls silently through to "{alias}.kamocrm.com". For Panda Express that produced panda-express-kamocrm-com while the theme had been written to pandaexpress-com. The wizard then waited its full timeout on a folder that would never exist and reported "your branding is still being applied", and opened the workspace naming a domain that resolves to nothing — so the shell fell back to the shared host and painted the platform's logo and colours over an organization whose own were already provisioned and waiting. Both symptoms, one guess. effectiveDomain is the row this request just created; the alias form is what resolvePrimaryDomain falls back to for an org with no domain, which is what provisioning uses for it. Either way this is the value rather than an inference of it.