Read client logs

Purpose

Read messages in the KKAuto desktop app Logs area at a customer operations level — for basic troubleshooting and support handoff. This page does not describe internal technical mechanics.

When to read Logs

• The app is not Connected or asks you to sign in again.
• A task was created but does not run or waits too long.
• The antidetect browser cannot open profiles.
• The machine slows down, browsers crash, or errors rise after increasing concurrency.
• Support asks you to send redacted logs.

How to read safely

1. Open the Logs area in the app (if shown).
2. Look at messages near the time of the issue.
3. Focus on customer-facing messages: connection, waiting tasks, browser, accounts to check, machine resources.
4. Compare with Facebook > Tasks and account status on the website.
5. Do not change advanced settings unless support instructs you.
6. When sending support: include only the relevant part and redact sensitive data.

What to redact before sending support

UIDs, emails, passwords, tokens, proxy values, 2FA codes, local URLs / ports, real account data, private names, and unrelated content.

What to do based on common messages

Visible message	What to do
Connection / sign-in unstable	Check website address, network, and login
Task waiting too long	Check task and account status; confirm Start Auto
Browser profile unstable	Check the browser provider; lower concurrency if overloaded
Many errors at once	Stop raising load; lower concurrency; note the time; contact support

See also

• Run Automation
• Task statuses
• Troubleshooting
• Update KKClient