What changed
Producer-side tools call this non-breaking. For a consumer it is a null dereference on an unknown future date.
Affects investigation_id on POST /accounts/{account_id}/cloudforce-one/v2/requests/{project_type}. Nothing fails at the call; it fails wherever the value is finally used, which is usually somewhere else entirely.
can now be null
Who is affected
Code that reads POST /accounts/{account_id}/cloudforce-one/v2/requests/{project_type} (investigation_id).
Before and after
| Where | Before | After |
|---|---|---|
| POST /accounts/{account_id}/cloudforce-one/v2/requests/{project_type} · investigation_id | string | null|string |
| GET /accounts/{account_id}/cloudforce-one/v2/requests/{project_type}/{request_id} · investigation_id | string | null|string |
| PUT /accounts/{account_id}/cloudforce-one/v2/requests/{project_type}/{request_id} · investigation_id | string | null|string |
Code that breaks
// response.investigation_id may now be absent or null const investigation_id = response.investigation_id ?? fallback;
Based on Cloudflare’s published API specification. How severity is decided.