RE: Plugin not triggering during data import
Like Bipin Kumar said, you can remove the Depth validation.
Reason is, Depth can help to prevent loops in recursive calls but it is not only used for that, it lets you know where you are in the execution path.
It works when you manually trigger it because you (the user) triggers the "create" request so, the execution path of this action that was manually/directly created is Depth = 1.
In your scenario, you (the user) starts an import job (Depth = 1), and then that process (import job) is sending the "create" request (Depth = 2).
In a hypothetical scenario where you trigger a Workflow or Plug-in (Depth = 1), then that process starts an import Job (Depth = 2), then you will have a "create" message with Depth = 3.
Hope this makes sense.
