Support

Flow Batch — troubleshooting, and how to reach a human

Write to mahdiferiani@proton.me. It is one person, so a reply takes a day or two. Telling me which Chrome version you are on and what the Queue tab said when it stopped will usually save a round trip.

Common problems

Nothing happens when a run starts, or every prompt fails at “Generate”

This is almost always Google changing Flow's interface. Flow is updated without notice, and when a button moves, the extension cannot find it any more.

The extension fetches a small file describing where Flow's buttons are, so this is normally fixed within a day without you updating anything — close the side panel, reopen it, and start again. If it persists past that, please write in, because it means the fix has not been published yet and you are the one telling me.

The run paused by itself

The tab being driven was closed, or navigated away. The run pauses rather than failing so nothing is lost: reopen Flow, pick the tab again on the Setup tab, and press Start. Start from # resumes without redoing the prompts that already worked.

Images are generating but not saving

Check the Setup tab's Subfolder in Downloads and Filename template. If Chrome is set to ask where to save each file, a long run will stack up dialogs and stall — turn off “Ask where to save each file before downloading” in Chrome's download settings for a batch to run unattended.

Chrome warns that the extension can “read and change” things, or asks about the debugger

Google Flow ignores clicks that software generates. Chrome's debugging interface is the only remaining way to press Flow's own Generate button, which is the one thing the extension exists to do.

It is attached only to the tab you selected, only while a run you started is in progress, and it is disconnected the moment the run ends. It never reads the page's data, never inspects network traffic and never runs code. The privacy policy says the same thing in more detail.

Some prompts produced fewer images than I asked for

Flow decides how many images a prompt returns, and it sometimes returns fewer. Raise Timeout per prompt on the Setup tab if images are still arriving when the extension gives up on them. Rows that failed outright can be re-run with Re-queue failed on the Queue tab.

A long run stopped partway with no error

Chrome can suspend a background extension on a machine under memory pressure. The queue is saved continuously, so nothing is lost: reopen the panel and press Start, and it picks up where it stopped.

Reporting something else

Useful things to include: your Chrome version, roughly how many prompts were in the queue, the message shown at the top of the Queue tab, and what you expected instead. Please do not send prompts or images you would rather not share — they are almost never needed to diagnose a fault.

Credits and billing

Flow Batch does not sell, meter or resell image generation, and it takes no payment. Generations are billed by Google against your own Flow account at whatever rate applies to you. Questions about Flow credits, quotas or billing have to go to Google; I have no visibility into your account.