Table API parameter 'sysparm_limit = 1' pick up record without consider if the user has access to it or not.Issue Table API call with :sysparm_limit=1 gives a blank response. This issue is happening on instances with HR module.ReleaseAny supported Release.CauseThis is the behavior by design, and the reason why no record is returned is caused by ACL. Despite what is expected that a Table API query including sysparam_limit=1 should return one record, this may not be necessarily true. The table information is returned from the database and we can’t control the order that this information is read. If for the first record returned the user does not have access based on the ACLs, this query won’t return anything. This is how GlideRecord works. 1. From the REST API, these parameters are passed into GlideRecord. 2. GlideRecord returns the limit set. 3. Then, the ACL does the evaluation. We don’t have control on how the data is returned, the first record found is picked up to be returned. This was designed to work in this way, preventing scenarios where that the search returned millions of records, and the system should evaluate security against every one of them to massage that number. This would never complete before the transaction timed out.ResolutionThis is the behavior by design. As workaround, an accessible record can be added to the query with the 'sysparm_limit = 1', forcing to return a record.Related LinksTable API