Logs
A running record of what the app did and what went wrong, used to track down problems.
What it is
Logs are timestamped lines an app writes as it runs: "user signed in", "payment failed: card declined", "error on line 42". They're the black box recorder for debugging.
There are usually two places to look: the browser console for frontend problems (what happened on the page) and server logs for backend problems (what happened behind the scenes).
If you can, paste the exact error from the logs into your bug report. It often points straight to the cause.
How to ask for it
“It failed but I don't know why.”
“The CSV import failed at 3:12 PM for a 2,000-row file. Check the server logs for that request and tell me the exact error, then fix it and log a clear message if a row is skipped.”
"Don't know why" leaves the builder guessing; pointing at the logs with a time and request narrows it down immediately.
You've seen this in
- YThe red errors in your browser's developer console
- HRequest logs in a hosting dashboard
- AActivity history in admin panels