REST Service debug logs

[Justin Abbott]

I need some assistance debugging REST logs. We are building a custom solution using AngularJS on a UI page. This page has an interface that allows users to create self-service incident records, that we're building using the REST API.

When I impersonate a non-itil user (the user only has the rest_service) role, they can submit the form and an incident gets created. We don't receive a response from the REST call, however.

Can anyone offer insight on the following debug logs?

06:22:21.645	Info	REST		API-thread-5 8F6FEC6D0F670200EF60847022050E6C Slow business rule 'Run SLAs' on incident:INC0769320, time was: 0:00:00.106
06:22:21.664	Debug	REST		API-thread-5 8F6FEC6D0F670200EF60847022050E6C DEBUG: [REST API] TableAPIService : Glide Record Insert Duration duration_micro_secs=743331
06:22:21.664	Debug	REST		API-thread-5 8F6FEC6D0F670200EF60847022050E6C DEBUG: [REST API] TableAPIService : Querying for inserted record
06:22:21.667	Warning	REST		API-thread-5 8F6FEC6D0F670200EF60847022050E6C WARNING *** WARNING *** Get for non-existent record: incident:NULL, initializing
06:22:21.669	Warning	REST		API-thread-5 8F6FEC6D0F670200EF60847022050E6C WARNING *** WARNING *** [REST API] TableAPIService : Created record can't be read. No Record found

Itil users are able to successfully create the incident and receive a response in the REST call.

[Justin Abbott · Accepted solution]

I ended up figuring this out. Multiple incident write ACLs were preventing certain users from writing to the table. The customization in our instance was the issue.