A batch you can stop

The task centre lives in the top bar of the app window. Its badge shows you what is running or waiting right now, and nothing else.

One batch is one row. You see the title with your count, a status chip, a bar while it runs, the tally so far and the time it last moved.

A flow running inside the app and a batch started from the list are two rows at once, and the badge shows you both.

A batch driven by the window walks your selection profile by profile. Cancel lands between profiles, so the profile already opening finishes and nothing after it is started.

A flow or a cookie robot run lives in the app itself, so the same button stops those too, not just a list of profiles. Your stop lands on the nearest step, and nested repeats and branches end with it.

1. 1

   You press it

   The button goes quiet: the stop lands after the current profile.

2. 2

   The item in flight finishes

   Cutting it off halfway would leave a browser half open or a record half written.

3. 3

   The rest are never started

   The batch ends on the count it had reached, not the count you selected.

4. 4

   The row settles

   You see it marked Cancelled, and the report names how many profiles really got through.

Cancel stops what has not started. It does not walk back what is finished, and there is no single press that puts two hundred profiles back the way they were.

Emptying the recycle bin is the case to think about. Cancel it halfway and the profiles already erased are gone, while the ones behind them sit in the bin untouched.

The tally lands on disk after each profile rather than being guessed from a clock. You see a slow batch moving instead of frozen.

The one case where the bar honestly stands still has a state of its own. When every browser window this machine allows is already open, you see Queued, and the queue waits for one to close.

A batch that finishes or fails leaves a line in the notification list, marked as finished or as failed. That line survives a restart, so a night run is still there in the morning.

If the window is not in front of you at that moment, the app also knocks through your operating system. That message is a way back rather than a report: pressing it brings the window forward, where the row with the tally is waiting.

An update ready to install, a schedule that could not run and a plan limit you reached leave the same kind of line.

Nothing here is resumed. A batch lives only while it walks your list, and the list goes when the program goes.

So on the next start you see every row that was still running or queued marked failed. Leaving it as running would be the worse answer, because you would wait for an ending that is never coming.

The rows themselves stay. You still find the last 50 tasks in place, so the morning after a night run tells you what happened.

Task rows and notifications sit in the app's own folder on your disk, where on macOS and Linux only your account can read them.

Neither one travels to your account, and this list has no server half. A second computer of yours keeps its own tasks and knows nothing about these.

Delete a profile for good and its name leaves the notification file with it, because a log you cannot see or clear is not a log you agreed to.