Hi @Sharad Srivast1,

Skipping script 'Printer Email Import', a suitable GlideRecord not found is expected when the Inbound Email Action is configured as a Record Action but no valid target record (current) can be identified.

• Record Actions require a target table and a valid GlideRecord context.
• Since your Target Table = None, the inbound email engine cannot create/find a current record and skips the script execution.

•  Record Actions require a valid GlideRecord (current) before the script is executed.

• Processing email attachments and loading Import Sets is supported, but it should not depend on a Record Action without a target record.

Email
   ↓
Inbound Email Action (Script)
   ↓
Attachment
   ↓
sys_import_set
   ↓
Transform Map
   ↓
IRE
   ↓
cmdb_ci_mfp_printer

A common pattern is to move the import logic into a Script Include and invoke it from the Inbound Email Action.

However, the root cause is the Record Action configuration, not the Import Set APIs.

 changing the Inbound Email Action design so it does not rely on a target record (current) and handles the attachment/import processing directly through script.