Bug: Due to replica lag, reading a newly created organization for serialization can fail, resulting in an empty response body on a successful 201 creation.
_{Severity: MEDIUM}

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: src/sentry/core/endpoints/organization_index.py#L446-L447

Potential issue: The organization creation endpoint can return an empty response body
with a `201` status code due to replica lag. The organization is provisioned on the
primary database via an RPC. Immediately after, the
`organization_service.serialize_organization` function attempts to fetch this new
organization for the response body. This read operation can be directed to a replica
database which may not have received the new data yet. This causes the serialization
function to return `None`, leading to an empty response body, which violates the API
contract expecting the new organization's data.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

Unhandled CellResolutionError in validate causes 500 error

Medium Severity

get_new_org_cell_for_locality in the validate method can raise CellResolutionError, which is not a DRF ValidationError. DRF's is_valid() only catches ValidationError, so this would bubble up as an unhandled 500 error. The field-level validate_dataStorageLocation properly catches CellResolutionError and converts it, but validate does not — both for user-provided values (where new_org_cell could reference a nonexistent cell) and for the settings.SENTRY_MONOLITH_REGION default (which bypasses validate_dataStorageLocation entirely and is not validated for existence, MULTI_TENANT category, or visibility).

 

^{Reviewed by Cursor Bugbot for commit b22ff7d. Configure here.}