Skip to main content

Resolving 404 Error and Migration Failure Due to Unsupported Property Type in Policy Configuration

This document describes how to resolve 404 Error and Migration Failure due to Unsupported Property Type in Policy Configuration

Issue: A user reported receiving a "Not Found" error (404) when attempting to use the Postman API for migration file extraction. The error message provided is as follows:

"type": "https://tools.ietf.org/html/rfc9110#section-15.5.5",

"title": "Not Found",

"status": 404,

"traceId": "00-0878d63dd8dc72647d9fdef58da68662-8c302a9b6546849e-00"

Resolution: Upon investigation, the following steps were taken to diagnose and resolve the issue:

  1. AWS Log Review:

    • After reviewing the AWS logs for potential errors related to the migration ID, an error was found indicating that the "Property type linkedSelectV2 is not supported. Mapping not found when trying to map policy data type 'linkedSelectV2' to migration data type in 'PolicyToDomainDataType'."

  2. Migration Status Check:

    • Using the migration status API (https://api.emea1b.fenergox.com/datamigrationquery/api/migration/{migrationid}), it was confirmed that the build-schema process had failed, while all other tasks were in a "waiting" status.

    • The error was traced to the unsupported property type linkedMultiSelectV2 in the policy configuration.

  3. Fix Applied:

    • After identifying the unsupported property type, the issue was resolved by changing the data type in the migration policy configuration. This allowed the migration to proceed successfully.

Steps to Resolve the Issue:

  1. Identify Unsupported Property Types:

    • Review the error messages in AWS logs or API responses for unsupported property types like linkedSelectV2 or linkedMultiSelectV2.

  2. Update Policy Configuration:

    • Modify the policy configuration to use supported property types. In this case, changing the property type in the policy configuration resolved the issue.

  3. Re-run Migration:

    • After updating the policy configuration, re-run the migration process and check the status to ensure that all tasks complete successfully.

Did this answer your question?