Skip to content

Wait with Chrome closed

Updated 2026-11-04Try the web sample

Reduce browser memory for qualified video jobs without resubmitting accepted work.

Chrome settings
Chrome settings · Real app screen with web sample data · App labels are currently in Vietnamese

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.
  • Start with one test video and keep track of its original profile and Queue entry.

Steps

  1. Find the waiting choice

    Open Cài đặt → Tạo tự động → Trong lúc Flow làm video. The choices are Giữ Flow mở, Chrome nghỉ nhẹ, and Tắt Chrome.

    Keeping Flow open retains its page until download finishes. Light waiting retains a lightweight Chrome page. Chrome-off waiting can close the app-managed browser after Flow accepts a qualified job.

  2. Test Chrome-off on a supported job

    Select Tắt Chrome, then send a small video job. Closing happens only after acceptance is recorded and a valid status read succeeds. The app keeps the profile’s own network route while waiting and downloading.

    Not every model, output count, or operation qualifies. Read the scope text beside the setting; unsupported combinations continue with Chrome rather than being blocked from creation.

  3. Let recovery follow the original job

    If status reading or downloading needs browser recovery, the app reopens the original profile and project to inspect or download the same accepted job, not to create another one.

    If Google requires sign-in or verification, complete it yourself. A needs-attention or waiting deadline is not proof that Flow generation failed.

  4. Keep concurrency conservative

    Việc cùng lúc mỗi hồ sơ applies only with Tắt Chrome. Its default is 1 and the setting permits up to 4. Raising it sends creation requests more densely to the same Google account; it does not increase Google entitlement.

    If you switch back to keeping Flow open, detached work returns to browser tracking rather than being cancelled or recreated.

When it worked

A qualified accepted job can finish with Chrome closed, or recover through its original browser without duplicate submission.

If something goes wrong

Why did Chrome stay open?

The operation may be outside the qualified scope, its status control may have failed, or you may be actively using the browser. The app keeps Chrome when closing is not safe.

Does Chrome reopening mean a second charge?

Recovery is intended to read and download the accepted job, not click Create again. Inspect the original job before deciding to retry manually.

Can this bypass Google checks?

No. Login, MFA, CAPTCHA, and account restrictions still require normal handling.