10 to 16 October 2026
This week we shipped timed pauses with automatic restart for High care processes, bots that now check their own work after every step, a page-copy tool that lets you fix a broken browser step without reopening the website, a full trial journey system to help new sign-ups reach their first result, and complete translations for eleven languages.
Pause a trigger for an hour, then let it switch itself back on
Switching off a trigger used to mean remembering to switch it back on. Miss that, and a High care process sits off all weekend with no one the wiser.
Pauses now have an end time. When you pause a trigger, a bot or a whole process, you choose how long: 30 minutes, one hour, four hours, until 07:00, or a time you pick. When the time is up, it switches itself back on and the pause history records "Automatically, at the end time".
High care processes go further. They can only be paused with an end time, and that end time can be at most eight hours (your admin can change the limit). If one is found switched off with no end time, the process owner is told within 15 minutes and reminded every four hours until it is back on.
Email, folder and queue triggers can now also carry a deadline. Set an at-risk window and a latest acceptable time on the trigger, and Automize tells the right people when the oldest waiting item is running late. A new Service levels page, linked from the process dashboard, shows every trigger's current state at a glance.
#Automize #ProcessAutomation #DigitalWorkers #Operations
Bots now check their own work after every step, not just whether they crashed
A bot that types a value into a field and moves on has no way of knowing whether the field accepted it, whether the email landed in Sent Items, or whether the database row actually changed. It reported success as long as nothing crashed.
Bots now check their own result after each step. A field still blank after typing fails the step. A Google Sheets write that changed no cells fails the step. A file copy is confirmed to be there in full. An Outlook email is checked in Sent Items. A Word replace fails if the text was not in the document.
You can also tell a step what should happen after it: an element appears, an element goes away, or some text shows, within a number of seconds you choose. If it does not happen, the step is retried like a failed click.
Run history shows the result of each check with a small mark: passed, differs, failed, or could not be read back. A summary panel counts how many steps checked their result and how many differed. Runs from older bots look exactly as they did before.
#Automize #DigitalWorkers #ProcessAutomation #Reliability
Fix a broken browser step by clicking the right element on a copy of the page
When a bot cannot find its button or field, someone usually has to open the website, find the right element, and update the step by hand. That means knowing which site, having access to it, and doing it while the problem is fresh.
With the new page-copy tool, the bot sends a picture of the page and the elements on it the moment a browser step fails. You open the failed step in run history, hover over the copy to see each element outlined, click the right one, and choose "Use this element". The step is updated and the bot retries it straight away. You never have to open the website.
This is switched off by default. An admin turns it on under Settings, Privacy and data, Bot privacy. The help text explains that the picture is sent even when error screenshots are off. Typed values are greyed out in the picture, frames from other sites are greyed out whole, and the page address keeps only the scheme, host and path. Sensitive steps are never captured.
#Automize #DigitalWorkers #BrowserAutomation #Operations
See what each new sign-up came for, and help them reach a first result
A free trial that ends without a result is a missed customer. Until now, the only way to know how a trial was going was to look at individual accounts one by one.
Sign-up now asks "What do you want to automate?". The New signups widget shows each workspace's answer, a status (new, active, stuck, quiet, paid), days left and what they have done. A summary email goes to staff every Monday morning.
New sign-ups get a welcome email matched to what they came for, and a trial banner with a one-time "Add 7 days" button. Get Started lists are matched to their answer, and the Help page has an Ask box that answers from our own help articles only.
When a trial ends, staff can now choose a free plan for the workspace to move to instead of a lockout. Follow-up emails (a nudge, an offer of a call, a trial-ending reminder and a win-back) are built and ready, switched off until staff turn them on.
#Automize #CustomerSuccess #Trials #Operations
The app is now fully translated in eleven languages, including Afrikaans and Arabic
Automize has had language files for years, but most were either empty or filled with English pasted in as a placeholder. This week we completed all 4,830 strings in eleven languages.
Afrikaans, Arabic, Chinese, Spanish, French, Portuguese, Russian, German, Italian, Dutch and Japanese now have every string translated. The only text left in English is product names, formula function names and format codes, all on purpose. Arabic is ready in the files but kept switched off for now, because the app does not yet have a right-to-left layout.
Afrikaans was redone from scratch. The old file had entries that were simply wrong, for example "Save As" had been translated as "Sanctions screening".
Translations arrive marked as machine-translated, waiting for a native speaker to review and approve them on the Languages page. The five South African languages (Zulu, Xhosa, Setswana, Swahili and Sesotho) are also done and waiting for review before being switched on.
#Automize #Localisation #SouthAfrica #Afrikaans