Skip to content
GFlow4AI
VIGet for Windows
Guide/Troubleshooting

Troubleshoot without duplicate work

Updated 2026-11-04Try the web sample

Find the failing stage before changing profiles or resubmitting an accepted job.

Problems show in the Queue
Problems show in the Queue · Real app screen with web sample data · App labels are currently in Vietnamese

Before you start

  • Keep the original job and profile identifiable.
  • Record the visible error without exposing passwords, cookies, or API keys.

Steps

  1. Check app and browser first

    If the app will not open, verify that the whole portable ZIP was extracted and launch FlowStudio.exe outside the ZIP. Review installation for unsigned-package warnings.

    If the app opens but Chrome does not, inspect Cài đặt → Chrome → Trình duyệt and select Chọn chrome.exe if needed.

  2. Separate network and account checks

    Inspect the configured proxy and its check result. Do not remove a proxy just to hide its error if that profile must use it.

    Open the original profile to handle Google login, MFA, or CAPTCHA yourself. A status-read 401/403 alone does not prove the proxy is broken or that Google signed the account out.

  3. Read Queue before retrying

    Find the job in Queue and read its reason. A queued job may be waiting for a profile, credit cap, concurrency slot, or an open Chrome when auto-start is off.

    For an accepted job, inspect or recover the original result before using retry or cancel. A tracking deadline does not establish that Flow failed.

  4. Check outputs and collect a safe report

    Inspect Library and the actual Thư mục kết quả. Distinguish generation failure from download failure; reopening the original Flow project can help inspect what already exists.

    When asking for help, include the app version, operation/model, approximate time, visible message, and whether Flow accepted the job. Remove proxy passwords, Google credentials, cookies, and API keys from screenshots.

When it worked

You have isolated the failing stage and a safe next action without blindly submitting the same work again.

If something goes wrong

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.

Chrome closed while Flow was working. Did the app crash?

Check the waiting mode. Tắt Chrome intentionally closes eligible app-managed browsers after acceptance and valid status checks. Follow the same Queue entry.

Should I resend when downloads fail?

First inspect the accepted job and its original Flow result. Download recovery can use the original profile; creating again is a separate request and can consume credits.