insert() method returning null

[Nisar2]

Hi experts,

A strange behaviour is driving me nuts. I've the following code inside a SI

var task = new GlideRecord('u_my_table');
task.initialize();
task.u_name = "Test";
var sys_id = task.insert();
gs.log(sys_id, "ABC");

The problem here is two fold:

1. Logs print the sys_id as null 1 in 50 tries (just a calculated guess)
2. Logs print the sys_id as expected the remaining times

So, I wonder what is causing it to fail that one time and if it is possible to know the reason why it failed?

I tried looking at logs (during the timeframe at which the insert happened) and did not find any warning/error level data.

[RAHUL Khanna1]

you can just log a if condition 

var task = new GlideRecord('u_my_table');

 task.newRecord(); // Try changing it to newRecord()

task.u_name = "Test";

var sys_id = task.insert();

if(!sys_id )

gs.log(task.u_name +"SysId: "+ sys_id )

--and can cehck for which name value it is givingn null value and then try creating the same record from background scripts, might get some hint.

[Sudhanshu Talw1]

One in 50 tries!Looks like Servicenow is unhappy.

Although it should return sys_id every time.

Record is getting created or not?

When it returns null

Thanks

Sudhanshu

[Nisar2]

No, record is not getting created when null is received.

[andymcdonald]

I just came across similar behavior today.  Mine happens with the cmdb_rel_ci table on Orlando, and yes, the record ALWAYS gets created successfully!  Have you opened a HI ticket yet?

[Hitoshi Ozawa]

The problem may be high load on your instance. Better contact HI and ask for their help.