Quit Browser

The Quit Browser block allows you to close the browser that your TaskBot is using.

You might not need this block. If your TaskBot uses a browser, the browser automatically closes when the TaskBot run ends (unless Stay on page after run is enabled in your TaskBot's Browser Launch Settings or a Launch Browser block).

How To Use It

This block works without configuration, but has one optional setting.

Force quit

When Force quit is checked, the browser instance is forcefully terminated regardless of whether other TaskBots are sharing the same browser instance.

Force quitting a browser context shared with a sticky profile used by other TaskBots will close the sticky profile for all TaskBots using it, not just the currently running TaskBot.

Things To Know

• A browser isn't required. If there's no browser context when this block runs, it logs a warning and continues. Your TaskBot won't fail.

• Sticky profiles are respected by default. If other TaskBots are sharing the same sticky profile browser, this block closes your tabs but leaves the browser running for them. The browser only fully quits when the last TaskBot using it leaves.

• Stay on page after run is overridden. Even if Stay on page after run is enabled in your Launch Browser settings, this block fully closes the browser. An explicit quit takes priority.

• You can relaunch after quitting. Placing an Open Link or Launch Browser block after a Quit Browser block launches a fresh browser context.

Block Behavior

• When a browser exists the block closes the browser and all its pages.

• When no browser exists the block logs a warning and continues.

• When a sticky profile browser is shared with other TaskBots the pages being used by your TaskBot are closed, but the browser stays running for other TaskBots.

• When Force quit is enabled the browser is terminated regardless of shared instances or Stay on page after run settings.