Debug Logs
Exactly what one caller received — the tool for “the agent said something wrong and I need to see what it was looking at.” Under Observe → Debug Logs.
Turning it on
Logging is time-boxed: you enable it for a window and it expires on its own. Payloads contain record data, so there is no way to leave it on permanently.
| Control | What it does |
|---|---|
| Enable logging | Opens a window — minutes, capped at four hours |
| Disable | Closes it immediately |
| Clear logs | Deletes every captured payload |
Each captured load shows Time (click it to open the payload), Entity, Version (blank means the load served from a never-activated draft — see Versions), Level, Surface, Format, Domain, User, Status, Tokens, Duration, and Warnings.
Debug a bad answer
- Enable logging for fifteen minutes.
- 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.
- Disable logging and clear.
WARNING
Logs hold real record data shaped by one caller’s permissions, and anyone with ContextWorks Admin can read them — possibly data they couldn’t reach through a normal query. Keep that permission narrow, and clear logs when you’re done.
Not an audit trail
Debug Logs is a debugging tool: time-boxed, self-expiring, and cleared on demand. If the question is what changed and who approved it, that is Writes, which is durable and expires never.