The Business Event gives a warning mark and requires manual execution.

​@apallawala21,

Could you please share the code behind the action you’re triggering this Business Event from?
It’s possible the issue is related to how that action is implemented, and seeing the code would help confirm whether it’s causing the null reference during event execution.

​@apallawala21 It is someerrors in the Business events-Import scenario configuraiton issue.

could you please revalidate the import scenario and verify,

Hi ​@VaheGhazaryan 

I am referring to the Action which can be entered through the Business Event. 

And I tried the same from Import Scenario with Excel upload, that works fine. 

Any difference if changing to “once for each record” instead?

​@MissyMain41 

I’ve tried that option, but it is still the same. 

Thank You

Alrighty, well I have seen business event get disconnected from the import scenario before. So perhaps  this could help:

1. Run request profiler (SQL logging included) and then trigger the BE - check Request Profiler → exceptions tab to see if it logged the object reference error and view the exception, perhaps something can be gleaned from it
2. Reboot the site to clear any back-end caching that may be related to GI screen ID changes, sometimes changing screen ID of a GI connected to a BE/Import can cause a disconnect between the import data provider that was built for the BE and the BE itself 
3. Rebuild the import subscriber directly on the BE itself, when rebuilding it you can use “insert from” to pull the configs from the broken import/provider to make it easier and faster and see if that helps connect the two again 
4. Instead of testing the import using excel provider manually, it would be best to test with “Generic Inquiry” data provider instead, and use the same exact GI that is associated with the BE