When I run Service Mapping, I receive an error: Invalid identification engine payload of endpoint

[Sandeep _]

When I run Service Mapping, I receive an error with for entry point: Invalid identification engine payload of endpoint .

[AJ-TechTrek]

Hi @Sandeep _ ,

The
 Invalid identification engine payload of endpoint error usually means that Service Mapping is passing incomplete or invalid CI data to the Identification and Reconciliation Engine (IRE) when it tries to create or update the Entry Point CI.

This happens most often when:
* Mandatory identifiers for the CI class are missing from the pattern output.
* The IRE payload has blank or invalid values for one or more keys in the Identification Rule.
* The wrong CI class is being sent for the endpoint.

Root Causes & Fixes

1. Check the CI Class & Identification Rule
1. Go to CMDB → Identification Rules.
2. Search for the class used by your entry point (e.g., cmdb_ci_endpoint, cmdb_ci_service_endpoint, cmdb_ci_url).
3. Check the Identification Rule:
* Look at the Identification Section → Mandatory fields.
* Typical endpoint identifiers:
* name
* ip_address or fqdn
* port (for TCP/UDP endpoints)
4. Fix: Ensure your pattern populates all required fields before cmdb_ci_endpoint or cmdb_ci_service_endpoint is sent to IRE.

2. Review Your Pattern Output
1. Open the Service Mapping pattern used for your entry point.
2. In the Debug log of the discovery, check the payload sent to IRE.
* Navigate to Discovery → Discovery Status → your run → Pattern Log.
3. If any mandatory fields are missing or null, update your pattern steps:
* Extract missing values (hostname, port, protocol).
* Use Set Values operations to populate fields.

3. Verify IRE Payload Format
* If you are populating endpoint CIs via Script in the pattern:
* Ensure the payload object matches the IRE JSON schema:
var endpoint = {
 className: 'cmdb_ci_endpoint',
 values: {
 name: 'myhost:443',
 ip_address: '10.1.1.5',
 port: 443,
 protocol: 'TCP'
 }
 };

* Missing name or wrong className will cause this error.

4. Watch for FQDN vs IP Address Mismatches
* If the identification rule expects fqdn but your pattern only returns an IP address, IRE will reject it.
* Either:
* Update the pattern to resolve fqdn (using a DNS step).
* Or modify the Identification Rule to accept IP + port.

5. Use IRE Debug Logging
Enable IRE debug to see the exact reason:
1. Go to System Properties → Identification Engine.
2. Set glide.cmdb.identification_engine.debug to true.
3. Rerun Service Mapping.
4. Check System Logs (cmdb_ire log source) for the exact payload and error message.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025