My TaskBot Does Not Start Run

PreviousCommon Problems NextWhen I Use Data from Table, No Data is Being Pulled

Last updated 3 months ago

Was this helpful?

My TaskBot Does Not Start Run

Common Causes

Not having the latest version of the agent. How to check if you have the latest version: How to Check Your Agent Version. You can install the latest version here: .
Expecting to see a user interface. The agent has no user interface. This is normal and intended. The agent just 'sits' on your toolbar on top right on Mac or bottom right on Windows. The actual building of the TaskBots takes place at .
Not noticing that the TaskBot ran. As soon as you click on the Run button to launch your TaskBot, a Chrome browser window pops up where the TaskBot runs. You have to click on it if it doesn't open automatically in front of you. And then you will see all the steps of your workflow happening in front of your eyes; otherwise, the TaskBot is probably running behind your other browser windows. You might want to switch on the "Stay on page" option for your first few runs because the run might take just a second or two, potentially going unnoticed (Stay on Page after Run).
Not having Chrome installed on your device. While you don’t need to use Chrome for building or launching TaskBots—you can do so from any browser—Chrome must be installed because TaskBots rely on it to run.
If you use creator.zerowork.io in a browser other than Chrome, you might need to disable shields or blocking settings in your browser. For example, in Brave, you may need to disable "Shields" in the settings. This is because the TaskBot builder sends requests to a local resource—the agent in this case—when you click the Run button. Some browsers, like Brave, may interpret these requests as non-secure and block them.
If you get the error "You need to first install agent (..)", this means that your agent is either not installed (see Install the Agent) or is not active. The most common issue that it is not active is because you need to double click on your agent to ensure it is activated and added to your toolbar (see ). Another common reason is initiating Run from a browser other than Chrome, which may block the request to the agent. To resolve this, refer to point 5 above.
Agent actually runs, it just runs with errors (for example, because you workflow set-up might be invalid). Open your run reports and check for errors. This is how you can access run reports inside the TaskBot that you are trying to run:

VPN interference. You might need to turn off your VPN when running TaskBots.
Firewall interference. You might need to turn off your firewall when running TaskBots.
Antivirus program interference. You might need to change to a different antivirus program or turn it off when running TaskBots.
Browser security settings—to resolve this, refer to point 5 above.
Enhanced security settings on your Windows device. While this is typically not needed, you might need to switch off reputation-based protection.

PreviousCommon Problems NextWhen I Use Data from Table, No Data is Being Pulled

Last updated 3 months ago

Was this helpful?

Common Causes

Not having the latest version of the agent. How to check if you have the latest version: How to Check Your Agent Version. You can install the latest version here: .
Expecting to see a user interface. The agent has no user interface. This is normal and intended. The agent just 'sits' on your toolbar on top right on Mac or bottom right on Windows. The actual building of the TaskBots takes place at .
Not noticing that the TaskBot ran. As soon as you click on the Run button to launch your TaskBot, a Chrome browser window pops up where the TaskBot runs. You have to click on it if it doesn't open automatically in front of you. And then you will see all the steps of your workflow happening in front of your eyes; otherwise, the TaskBot is probably running behind your other browser windows. You might want to switch on the "Stay on page" option for your first few runs because the run might take just a second or two, potentially going unnoticed (Stay on Page after Run).
Not having Chrome installed on your device. While you don’t need to use Chrome for building or launching TaskBots—you can do so from any browser—Chrome must be installed because TaskBots rely on it to run.
If you use creator.zerowork.io in a browser other than Chrome, you might need to disable shields or blocking settings in your browser. For example, in Brave, you may need to disable "Shields" in the settings. This is because the TaskBot builder sends requests to a local resource—the agent in this case—when you click the Run button. Some browsers, like Brave, may interpret these requests as non-secure and block them.
If you get the error "You need to first install agent (..)", this means that your agent is either not installed (see Install the Agent) or is not active. The most common issue that it is not active is because you need to double click on your agent to ensure it is activated and added to your toolbar (see ). Another common reason is initiating Run from a browser other than Chrome, which may block the request to the agent. To resolve this, refer to point 5 above.
Agent actually runs, it just runs with errors (for example, because you workflow set-up might be invalid). Open your run reports and check for errors. This is how you can access run reports inside the TaskBot that you are trying to run:

VPN interference. You might need to turn off your VPN when running TaskBots.
Firewall interference. You might need to turn off your firewall when running TaskBots.
Antivirus program interference. You might need to change to a different antivirus program or turn it off when running TaskBots.
Browser security settings—to resolve this, refer to point 5 above.
Enhanced security settings on your Windows device. While this is typically not needed, you might need to switch off reputation-based protection.