Debug Logs
Exactly what one caller received. Open it when an agent said something wrong and you need to see what it was looking at. Under Observe → Debug Logs.
Turning it on
Logging is time-boxed: you turn it on for a window, and capture stops on its own when the window closes or at 500 stored rows, whichever comes first. Payloads hold record data, so there is no way to leave it on permanently.
| Control | What it does |
|---|---|
| Log 15m · Log 60m | Starts capture for that window |
| Stop | Ends capture immediately |
| Clear | Deletes every captured payload |
Each captured load shows Time (click it to open the payload), Entity, Version (blank means the load served a draft rather than an active version — see Versions), Level, Surface, Format, Domain, User, Status, Tokens, Duration, and Warnings.
Debug a bad answer
- Click Log 15m.
- Have the user reproduce the problem.
- Open the payload they received.
- Compare against your own preview of the same record. Preview runs as you; if the log is missing fields your preview has, it’s FLS.
- Click Stop, then Clear.
WARNING
A payload holds real record data, shaped by the permissions of the caller who received it. Clear the logs when you’re done.
Notes
- A payload opens under its own rules. The page is admin-only, and it lists every captured load, but the payload itself opens only if you ran that load yourself, you hold View All Data, or you can read the record it captured. Otherwise the row stays closed and says why.
- A Find Records log captures many records at once, so access can’t be checked record by record. Those payloads open only for the person who ran the query, or for someone with View All Data.
- This is a debugging tool, not an audit trail. For what changed and who approved it, use Writes, where nothing expires.