FMS_APP
(Fms App)
1
Hi Team
Please check that our application got one issue with below repsonse code:
{“code”:0,“message”:“Failed to run code in sandbox on behalf of application’s system user.”,“errorData”:{}}
Is that Backendless end error ? Kindly check
Our application ID: 96A33344-0C65-AC14-FF0D-C71CD4DDCA00
Best regards
Nyi Nyi Lin
Marina.Kan
(Marina Kan)
2
Hi, @FMS_APP
We are sorry for the inconvenience. Our team is working on it. This problem is of the highest priority for us.
Regards,
Marina
Marina.Kan
(Marina Kan)
3
@FMS_APP, The issue that you wrote about above has been fixed from our side. Can you confirm that everything is working as it should now?
Regards,
Marina
The issue has been fixed from our side.
Could you please check if it works fine now?
Regards,
Olha
Hello @olhadanylova,
We are also experiencing the same error. It occurs in one of our methods, BackendlessLoginAuthRest.

Please check. Thank you!
APP ID: 4A47197B-AE30-FA84-FF56-0071F4010900
Francis,
What is the name of the service?
Does the method accept any arguments? If so, what values should we use?
We need to be able to reproduce the error in order to understand what happened.
Regards,
Mark
Hello Mark,
Thank you for checking. We have this in the BG_01_ADMIN service, but the main logic resides within the function itself.
The function does accept arguments, and you can use the object below as input.
{
"action": "update",
"method": "LeadUpdateEvent",
"requestType": "serverSide",
"createObject": {
"sdr": "Fred",
"state": "United States, Florida",
"region": "US",
"school": "⏳ Alexis/Andreas",
"status": "enrolled",
"service": "Microschool",
"objectId": "36164F41-42D3-4763-B98C-D6F3475D23FA",
"timezone": "US/Eastern",
"chargebee": "cus_RnVJ8o3*******",
"parent_name": "Meriyam"
},
"databaseName": "weekly_slots"
}
Hi Francis.
I ran the function and received a response. I need to be able to reproduce the problem. Do you know what conditions could trigger it?
I’m not sure what could have triggered it, since it was working fine before and the logic hasn’t been updated.
We’re now encountering a “socket hang up” error as well.

Does it happen every time for you? I tried just now and got a valid response from the server.