Symptom
A POST request to create a new High Performance Routing (HPR) profile returns a success response. However, when querying the list of existing HPR profiles, the newly created profile does not appear.
Cause
The most common cause is a mismatch between the scope used during creation and the scope queried when listing HPR profiles. If the HPR was created with "scope": "globalscope" but the list query targets a different scope (or vice versa), the profile exists but is invisible in the listing.
A secondary cause is that the HPR build process runs asynchronously. The success response confirms the creation request was accepted, but the profile may not yet be fully built and indexed when the list is queried immediately after.
Resolution
1- Verify the scope — confirm the SCOPE value used in the creation payload matches the scope filter applied when listing HPRs. Example creation payload used in this case:
{
"label": "Van with tunnel restriction B",
"scope": "globalscope",
"storedProfile": "default",
"requestProfile": {
"featureLayerProfile": {
"themes": [
{ "id": "PTV_TruckAttributes", "enabled": true }
]
},
"vehicleProfile": {
"load": {
"tunnelRestrictionCode": "B"
}
}
},
"coordinateFormat": "EPSG:4326",
"highPerformanceRoutingNetworkOptions": {
"geographicRestrictions": {
"allowedCountries": ["DE", "FR"]
}
}
}2- Wait for the build to complete — HPR construction is asynchronous. Query the HPR status endpoint using the ID returned in the creation response to confirm the profile status is READY before listing.
3- Query by ID directly — use the HPR ID returned in the creation response to retrieve the profile directly and confirm it exists, independently of the list endpoint.
4- Check that the full requestProfile is included — an incomplete profile (e.g. missing tunnelRestrictionCode or PTV_TruckAttributes) may cause the build to fail silently. Ensure the full profile is provided at HPR creation time, as shown in step 1 above.
Related articles
PTV xServer: ADR tunnel restrictions not applied in planTours when using ExistingDistanceMatrix
PTV xServer 2: Height Violations Disappear or Route Changes When Adding a Waypoint