getting Failed machine identity validation for table sys_import_set error

[osmantaken1]

Hi Everyone,

I’m working on an eBonding integration using the Import Set API in ServiceNow and running into a Machine Identity Access Control issue.

Scenario

• Created a custom staging table extending sys_import_set_row

• Using Import Set API endpoint:

  /api/now/import/<staging_table>

• REST API Policy configured for:

  • API Type = Import Set API

  • All Resources = true

  • All Methods = true

  • All Versions = true

• Integration user has roles such as:

  • import_admin

  • import_transformer

• Machine Identity Access Control is enabled

What is happening

When Machine Identity Access Control is enabled, the API response returns:

{
  "error": {
    "message": "Action is not authorized",
    "detail": "Failed machine identity validation for table sys_import_set"
  },
  "status": "failure"
}

However, despite the error:

• Records ARE successfully inserted into the staging table

• Transform map executes successfully

• Incident records are also getting created successfully

So functionally everything works, but the API response still returns the authorization error.

Additional observations

• If I disable Machine Identity Access Control, the error disappears completely

• I cannot see sys_import_set or sys_import_set_row available in the MIC resource selection list

• This does not appear to be an ACL issue because inserts and transforms succeed successfully

• The issue seems to happen during some internal Import Set API processing/validation step

Question

Has anyone faced this issue specifically with:

• Import Set API

• Machine Identity Access Control

• Failed machine identity validation for table sys_import_set

Is there any additional configuration needed for internal import tables, or is this a known platform limitation/defect with MIC + Import Set API?

Any guidance would be appreciated. Thanks!

[MohiniV]

I am also facing the same problem can anyone help on this

[MohiniV]

Please anyone know this issue and its solution provide the details

[osmantaken1]

I added the tables sys_import_set or sys_import_set_row that are not available in the list field using background script.