Version 1.1.68

Agent version is now included in error reports (both in the UI and notifications).
Added a new option in the File Options for the Take Screenshot and Save File building blocks to customize the maximum time that the TaskBot should wait for the file to fully download. The default is 5 minutes for Save File and 2 minutes for Take Screenshot. If the file isn't downloaded within that time, an error will be raised.
You can now set midnight as the end time in the scheduler's time range option.

Added automatic retry on 502 errors and aborted response streams.
The Open Link building block now automatically retries on certain network errors (e.g., tunnel connection failures with flaky proxies).
The scheduler in the desktop agent now has a more robust retry mechanism. For example, if syncing scheduled tasks fails due to an internet connection failure, it will retry more persistently.
When copying building blocks to another TaskBot, table references are now preserved if both TaskBots share the referenced table. (However, this does not yet apply to variables with the same name.)
The Write JS block now cleans up its context only after the delay period defined in the "min" and "max" fields has finished, giving more time for non-awaited async code to finish.
Notification settings are no longer duplicated when a TaskBot is duplicated.
Improved handling of parallel webhook triggers, covering more edge cases to prevent duplicate run triggers.
Improved handling in the Open Link building block for rare timing cases where a page crashes or closes just before reuse. The building block now reliably detects the closed state and starts a new context as needed in such cases.
Improved concurrency control when multiple TaskBots try to initiate non-incognito browser runs simultaneously.
Several error messages have been improved for clarity.

When a Check Web Element building block was deactivated and later used as a new start point via "Start run from here," the related Found and Not Found building blocks stayed deactivated.
In version 1.1.61, the Save File block introduced file-awaiting logic, but this did not apply to the option "From download action". Now fixed: Files are awaited for both options "From download action" and "From file URL".
Fixed a rare case where a run could be displayed with an unknown or non-terminated state in the TaskBot run reports if the start-run request succeeded but an unexpected error occurred after that yet before the run state was initialized.

Includes fixes for breaking changes introduced in 1.1.61:

Last updated 13 days ago

Was this helpful?

Agent version is now included in error reports (both in the UI and notifications).
Added a new option in the File Options for the Take Screenshot and Save File building blocks to customize the maximum time that the TaskBot should wait for the file to fully download. The default is 5 minutes for Save File and 2 minutes for Take Screenshot. If the file isn't downloaded within that time, an error will be raised.
You can now set midnight as the end time in the scheduler's time range option.

Added automatic retry on 502 errors and aborted response streams.
The Open Link building block now automatically retries on certain network errors (e.g., tunnel connection failures with flaky proxies).
The scheduler in the desktop agent now has a more robust retry mechanism. For example, if syncing scheduled tasks fails due to an internet connection failure, it will retry more persistently.
When copying building blocks to another TaskBot, table references are now preserved if both TaskBots share the referenced table. (However, this does not yet apply to variables with the same name.)
The Write JS block now cleans up its context only after the delay period defined in the "min" and "max" fields has finished, giving more time for non-awaited async code to finish.
Notification settings are no longer duplicated when a TaskBot is duplicated.
Improved handling of parallel webhook triggers, covering more edge cases to prevent duplicate run triggers.
Improved handling in the Open Link building block for rare timing cases where a page crashes or closes just before reuse. The building block now reliably detects the closed state and starts a new context as needed in such cases.
Improved concurrency control when multiple TaskBots try to initiate non-incognito browser runs simultaneously.
Several error messages have been improved for clarity.

When a Check Web Element building block was deactivated and later used as a new start point via "Start run from here," the related Found and Not Found building blocks stayed deactivated.
In version 1.1.61, the Save File block introduced file-awaiting logic, but this did not apply to the option "From download action". Now fixed: Files are awaited for both options "From download action" and "From file URL".
Fixed a rare case where a run could be displayed with an unknown or non-terminated state in the TaskBot run reports if the start-run request succeeded but an unexpected error occurred after that yet before the run state was initialized.

Includes fixes for breaking changes introduced in 1.1.61:

Last updated 13 days ago

Was this helpful?