Transform Map: Ignored Row Still Inserts Target Record

[JosephW1]

Hello,

First, I will establish some basics that are probably floating to the top of your mind:
1. The transform map is setting ignore to true when action == "insert".
2. If I look in the Import Set Row [sys_import_set_row] table for row 42,052, its State is "Ignored".
3. If I look in the Transform History for the given transform, the ignore count is 25k+.
Points 1-3 should help establish that this isn't a "Please teach how to ignore an import set row" question, as the ignore feature is already in use as shown by the transform history, but this is rather a troubleshooting-assistance question.
4. However, if I go to the target table, there is a record there that A) matches up to the Import Set Row 42,052 mentioned earlier, B) was created by the unique user that runs the transform, C) was created during the transform's execution, and D) was created at the exact moment that the Import Set Row was updated(!).
5. In the target table I can find similar ignored-yet-inserted target records dating back to late Feb 2022, but none before that point. The table dates further back than Feb 2022, so this likely indicates the onset of this symptom.

I haven't yet identified any relevant changes in our environment that occurred in late Feb 2022, nor have I yet found any documentation on what to do when inserts circumvent the ignore mechanism like this, so that's why I'm bringing this question here.

To date, here is where I've looked for the culprit:

1. GlideRecord.updates in transform map field maps or transform scripts. Nope. -Thanks @palanikumar 
2. GlideRecord.updates in BRs/script includes that could be triggered by this transform map. Nope

Any ideas on what is causing this malfunction, please? Thanks!

Kind Regards,
Joseph

[Shui]

I am having a similar issue. I imported/transformed about 2K records to an empty target table. All records were inserted to the target table, the number of records in the Import Set matches that of the target table. However, when I looked at the State in the Import Set, about 17 records are Ignored and 7 are Updated, though all of them should be Inserted. Would like to know what the cause of it. 

[JosephW1]

Your issue sounds like normal behavior. If your coalesce column was uuid below then the sample set below would create 3 inserts, 2 updates, and 1 ignore.

row	uuid	name	[result]
1	abc123	test	insert
2	bcd123	test	insert
3	cde123	test	insert
4	abc123	test2	update (row 1, name changed)
5	bcd123	test2	update (row 2, name changed)
6	cde123	test	ignore (row 3, no change)

[Shui]

I thought of that. But there was no duplicates of the coalesce column in the import file though. And I cleared the import set and target table, and ran the same import again, and all are inserted in import set this time.