Read profile status
On this page · 6 steps
Distinguish browser state, account readiness, network health, and job progress.
Before you start
- Open the desktop app, not the website preview with sample data.
- Know which Google account and network route this profile should use.
Steps
Identify the right card
Locate the profile by its name and avatar. Check its network information before acting. Do not diagnose a stalled job from a different account’s Chrome window.
The app keeps each profile’s Chrome data separate.
Session states distinguish likely signed in, needs Google sign-in and unknown. Chrome states distinguish plain open, controlled open, starting, stopping, error and stopped; an ordinary controlled-running card can omit the Chrome chip. Error or proxy-error summaries take priority over ready/running summaries.
Profile cards with session, Chrome and proxy statusReal app screen · web sample data · private details blurred Separate browser state from sign-in
An open Chrome process does not by itself prove that Google sign-in or Flow access is ready. If plain sign-in is in progress, finish it and click Done, open to work.
Use Google sign-in if Google asks for login or verification.
The More actions menu of a profile cardReal app screen · web sample data · private details blurred Check network and credit separately
A successful proxy check measures that route, not the account’s eligibility. Read errors where they occur and review credit and cost before assuming a displayed balance permits the next job.
Local credit caps can stop submission even when Google has credits available.
What websites see from a profile's ChromeReal app screen · web sample data · private details blurred Inspect the job itself
Open Queue for the job’s progress and message. With Chrome-off waiting, a closed browser can be normal while Flow continues working.
Use Screens or Live viewer when a controlled browser is available; do not recreate a job simply because no browser image is visible.
Watching and controlling one profile's ChromeReal app screen · web sample data · private details blurred Find and repair the right card
Use the profile filters and search by name or note. The need-sign-in filter includes unknown sessions; reset the search if the card disappears. A failed card offers Fix proxy only for proxy errors, otherwise Edit profile; a saved proxy check may be older than the current route.
Profile cards with session, Chrome and proxy statusReal app screen · web sample data · private details blurred Close before deleting
Finish jobs, close Chrome and wait until it has stopped before deleting from the profile menu. Confirm the named profile only if you intend to remove its Chrome data and metadata; there is no undo. If folder removal fails, wait a few seconds for background Chrome to exit and try again.
The More actions menu of a profile cardReal app screen · web sample data · private details blurred
When it worked
You can identify whether the next action belongs to Chrome, Google sign-in, the proxy, or a particular job.
If something goes wrong
The browser is closed but the job is running. Is that wrong?
Not necessarily. With Chrome-off waiting, accepted qualified jobs are tracked without Chrome. Check the job’s message and selected waiting mode.
Can I continue if the proxy fails?
Repair or check the configured proxy first. The app does not silently switch a proxy profile to your real IP.
Where should I check the current state?
Return to the original profile card and Queue before repeating an action. Read any visible error and preserve accepted work.