I have an Object Script Trigger named 'createrecord on object 'test1' where it will create a record to object 'test2'. I don't put a timing property on the trigger. When I run the trigger using the Run Triggers on the Trigger Section, i'm recieving an email notification containing an error message: Error executing Trigger: "createrecord" Error Error creating test2: null (line #6) in formula: Here's my trigger formula: var x = new Array(); x["name"] = 'scheduler'; rbv_api.createRecord("test2", x);
This is now fixed in codebase.
I've got a new error message.
Error executing Trigger: "createrecord" Error Error: Execution time 3546 ms exceeded allowed 3000 ms in formula:
The error always occur on this line of code:
var rbv_api = new Packages.com.rb.core.services.api.ServerSideAPI(50528652, 50571631);
What's the problem? Thanks for the reply
I've got a new error message.
Error executing Trigger: "createrecord" Error Error: Execution time 3546 ms exceeded allowed 3000 ms in formula:
The error always occur on this line of code:
var rbv_api = new Packages.com.rb.core.services.api.ServerSideAPI(50528652, 50571631);
What's the problem? Thanks for the reply
Try to make your triggers more efficient or increase time limit for formulas.
Can you make your logo more decent? This is not a gaming forum.
probably on our internet connection. still though error message is appearing on this code:
var rbv_api = new Packages.com.rb.core.services.api.ServerSideAPI(50528652, 50571631);
There is a setting on your server which controls max execution time. I cannot help with that since I'm not your sysadmin.
Thanks but the execution time is no longer an issue. The problem is I can't create records when not using timing property but by hitting the Run Triggers button on the Trigger Section. I also tried executing the trigger on .com, and still, it can't create a record and sends an error message.
I'll send a support ticket, i'll let you know when its done. Thank you
You're trying to create 1000 records. Each record gives you an error due to a bug in the code which is not fixed yet on .ph server (will be fixed after the next software update). No wander you're having timeout.
Please do not work with this piece until the next software update - you're only draining away server's resources and slowing down work of other users.
Support ticket done
So just wait for .ph server update.