GlideRecordSecure implementation is causing issues on some querybuilder scriptsDescriptionThis issue originated from the changes put in as part of DEF0267001. The script function is broken as sys_trigger job is not cleaning up data from table. The fix is to replace GlideRecordSecure with the combination of using GlideRecord class and checking access with canRead() before querying the data.Steps to Reproduce 1. Populate some data in qb_query_status and qb_saved_query by saving some queries in query builder UI.2. Adjust qb table cleaner job so it can run within short reasonable time.3. Let the table cleaner job run or execute it directly. The job fails to clean up the table.WorkaroundFollowing changes need to be made for script includes named "QueryBuilderReports" and "QBStatusRecordsToDelete": Go the each of those script include files and replace the occurrence of GlideRecordSecure with GlideRecord and in the following line, add this check: if(!<GlideRecord var name>.canRead()){ return []; } e.g. in the script QBStatusRecordsToDelete, the occurrence: var glideSavedQuery = new GlideRecordSecure('qb_saved_query'); needs to be replaced with: var glideSavedQuery = new GlideRecord('qb_saved_query');if(!glideSavedQuery.canRead()){return [];}Related Problem: PRB1588204