Troubleshooting
Find the message or symptom you see. Each entry says why it happens, what to check and how to fix it.
In short
On this page you can
- Fix access, loading and export problems of the audit log.
- Understand why a list is empty or a record has no fields.
- Find out why a change you expected is not in the log.
How to use it
- Find the message or symptom below.
- Open the entry and follow Check, then Fix.
- Still stuck? Write to info@smartestqa.ai with the Request ID of the record.
Logs#
Logs is greyed out: “Please contact your administrator to access this feature.”Access
- Why
- The audit log is for Admin and Super Admin.
- Fix
- Ask an admin to look up the change, or to give you the Admin role. See Screens that need Admin.
I see only the Audit logs tabAccess
- Why
- The other tabs (system logs and AI usage) are for SmartestQA operators. Everything about your company’s changes is in Audit logs.
“Audit records could not be loaded.”Loading
- Check
- Your session is still valid; the date range is not reversed (From after To).
- Fix
- Click refresh, or reload the page and sign in again.
“No records for these filters.” or “No changes recorded yet. Recording starts when this version is installed.”Loading
- Why
- The filters exclude everything, or the change happened before audit recording was installed on your SmartestQA.
- Fix
- Click Clear filters and widen the dates. Older changes are not in the log.
A change I expected is not in the logLoading
- Why
- Only changes are recorded. Opening a page, searching, previews, connection tests, AI chat and machine traffic (agents, runners) are not. Results that the runner writes during a run are not changes by a person.
- Check
- Search for the record’s name without other filters; try Source = MCP (Claude) or API key.
- More
- What is and is not recorded.
A record shows “Not recorded for this action (no fields, or the screen may hold secrets).”Details
- Why
- The request had no fields, or it came from a screen that can hold secrets (users, sign-in, data sources, integrations, mobile configuration and others). Their values are never stored.
- Fix
- Use who, when, area and record to trace the change. See Sent fields.
Some sent fields show ***Details
- Why
- The field name looks like a secret (password, token, API key, credential, cookie…). It is masked on purpose.
“Export failed.” or Export CSV is greyed outExport
- Why
- The button is greyed out when the list is empty or an export is running. A failure is usually an expired session or a blocked download.
- Fix
- Reload, allow downloads from SmartestQA, and narrow the date range: one export holds at most 50,000 records. See Export as CSV.
Didn’t find your answer?Write to support with your project name and what you see on screen.
info@smartestqa.ai