---
sourceDocument: Australia Telecommunications Network Inventory
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/telecom-network-inventory

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Telecommunications Network Inventory

ft:clusterId :

    - telninv

bundleId :

    - telninv

workflow :

    - Customer and Industry


---

# Data center infrastructure allocation failure cases

# Data center infrastructure allocation failure cases {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Allocation failures occur when devices, rack constraints, or CMDB records don't meet the requirements for placement.

## Allocation failure cases {#data-center-infra-allocation-failure-cases__section_sb4_2rq_tjc}

* Each device listed in the request must exist as a hardware configuration item in the CMDB, with a matching equipment model record that includes a rack unit count. If any device or its equipment model is not found, the allocation fails. Work notes list which records are missing.
* A write-back to the CMDB is blocked by a platform rule. In this case the run is reported as a failure even if a placement was found.
* If no single rack can accommodate a device, the allocation fails even if the combined capacity across multiple racks is sufficient.
* If splitting is not allowed and no single rack fits the full request, the allocation fails.
* No rack units or devices are specified in the short description and description of the change request.
* The placement policy cannot be interpreted and the allocation cannot proceed. A warning appears in the Decisions section of the work notes.
* No rack --- or combination of racks when splitting is allowed --- can satisfy the rack unit, power, weight, contiguous space, or temperature constraints.
{#data-center-infra-allocation-failure-cases__ul_e4m_n3w_zjc}