---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Resolve pattern-related mapping errors

# Resolve pattern-related mapping errors {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can troubleshoot mapping errors caused by patterns.

## Before you begin

Verify that the mapping error is caused by an inaccurate pattern by checking the
discovery message. If the message says "Failed to recognize application", the error
is pattern-related.

You need to be familiar with the Pattern Designer module of Service Mapping.

Role required: admin and service_mapping_admin

## About this task

If there are configuration items (CIs) that Service Mapping could not
map correctly, they appear on your service instance map with
warning icons ![The warning icon](). Typically, mapping errors happen when Service Mapping fails
to connect to a CI or fails to recognize it due to an inaccurate pattern.

You can identify problematic steps in your pattern and fix them without reviewing all
steps and operations contained in the pattern. It allows you to troubleshoot
pattern-related errors quickly and effectively.

## Procedure

1. Open the service instance map.
   1. Navigate to AllCSDMManage Technology Management ServicesService Instance. {#t_TBSMapProcess__NavigateCSDMManageTechServiceAppService}
   2. Select the needed service instance.
   3. On the service instance page, select View Map.
   {#t_TBSMapProcess__substeps_xxr_jpz_dmb} {#t_TBSMapProcess__Cmd_NavigateToAppServicesSM}
2. Ensure that the map opens in Edit mode displaying discovery messages and errors.  

   <br />

3. Right-click the CI with the warning icon (![The warning icon]()) and select Show discovery log.
4. Expand the failed pattern which appears above the result marked red.  

   <br />

5. Expand the failed section and click the failed step.  

   <br />

6. Click Debug.
7. Click the first step and wait for Pattern Designer to run it.  
   Repeat this action for other steps following the order until you reach the faulty step that causes the error.

   In the example below the port number is 8081 instead of 8080 which causes the problem.  

   <br />

8. Click OK.
9. Fix the pattern attribute that causes the problem.
10. Click Test.
11. Verify that Pattern Designer returns a success message.
12. Click Save.
13. Click Activate.
14. Return to the service instance map which contained the mapping error.
15. Right-click the CI for which the pattern was fixed and select Resume discovery.
16. Verify that the CI is discovered and mapped correctly.
**Related tasks**   

* [Fix service mapping errors using discovery messages](https://servicenow-prod.fluidtopics.net/Kw88zdxkkI61hdgabLIlCw "Service Mapping does not offer semi-automated resolution options for errors that require advanced resolution. Fix such errors using symptoms and discovery messages.")
* [Skip errors to continue discovering an application service](https://servicenow-prod.fluidtopics.net/2Bqj4Q5MPMcgcVdF4HtITQ "If you know what configuration items (CIs) and connections make up your service instance, you can enable Service Mapping to continue discovery of the service instance even if there are some errors. You can skip errors to troubleshoot later so you can complete mapping most of the service instance, even if some CIs are missing.")

*[\>]: and then