7 to 13 November 2026
This week we made document reading noticeably more accurate, fixed shared processes running the wrong version, repaired co-editing so reloads no longer drop steps, brought recipe document conversion to cloud flows with OneDrive and SharePoint support, and stopped the bot from giving up on pages that simply loaded a little slowly.
Document reading is more accurate: fewer wrong figures, fewer missed rows
When a bot reads an invoice or supplier statement, small differences in how a document is laid out can trip up the AI. A figure from one row ends up on another, a credit note loses its minus sign, or a part-read page comes back empty and the rest of the document is quietly dropped.
We worked through 174 real documents this week and fixed a set of these patterns. A long invoice that was read in parts now retries any part that comes back empty or too short, rather than silently dropping it. Rows the AI left out of a statement are recovered from the printed page and added back, but only when the statement then adds up correctly. Dates printed in the format 11.11.24 are no longer misread as the amount 1111.24.
Across our test set, invoices went from 96.5% to 97.0% accuracy and statements from 95.8% to 97.1%. The number of wrong fields dropped from 782 to 138, and 9 more documents now read at 100%.
If your bots read invoices, purchase orders or statements, they will pick up these improvements automatically on the next run.
#Automize #DocumentAutomation #InvoiceProcessing #Accuracy
Shared processes now run the right version for every company
If your company runs a process that is owned and maintained by another organisation, you may have noticed it running an older version even after a newer one was promoted. We tracked this down to where the promotion record was being saved: it was filed under the promoting company's environments rather than the process owner's, so every machine and every trigger kept picking up the previous version.
We fixed how promotions are recorded and read. Now, whichever company promotes a shared process into an environment, the newest promotion is what everyone runs. The promotion ladder, the run trigger and the bot's own readiness check all read through the owner's environments consistently.
This matters most for finance and operations teams who rely on centrally maintained processes, such as accounts payable or reconciliation flows, where running a stale version can mean missing a fix or a new step entirely.
#Automize #ProcessAutomation #Operations #DigitalWorkers
Co-editing a process map no longer drops steps when a browser reloads
When two people had the same process open at the same time, reloading one browser could pull both editors back to only the first few steps. Arrows drawn by one person would disappear from the other's view, and moves made after the second editor joined would never arrive on the first editor's screen.
We found four separate causes and fixed all of them. The shared copy of the map now only adds new content rather than overwriting what is already there. Remote changes remove only the arrows a peer actually deleted, not every arrow the shared copy does not hold. Edits made after the second editor joined are now sent correctly. And a page that joins a session where someone is already working no longer pushes that person's steps back to where they were before.
We tested this with two browser tabs over five quick reloads. All 32 steps and all arrows held every time. On the previous code, steps and arrows were being lost.
#Automize #ProcessDesign #Collaboration #Reliability
Cloud flows can now convert documents with a recipe, including files from OneDrive and SharePoint
Until now, converting a document using a recipe, the "Convert by example" approach where you show the system one example and it learns the pattern, required a bot running on a machine. That ruled it out for lightweight, trigger-based flows that run entirely in the cloud.
We have added a new cloud step that follows the same recipe through the document service, with no bot needed. A typical use is watching a mailbox, converting the attachment using a saved recipe, and saving the resulting file. We also added steps to list files in a folder and to work with files in OneDrive and SharePoint, including saving, finding a SharePoint site, listing a folder and downloading files.
Two ready-made templates are included: one for converting email attachments with a recipe, and one for converting files in a folder. The feature is available now for cloud processes. Document conversion is charged per page, the same as the manual Convert tab.
#Automize #CloudAutomation #DocumentProcessing #Microsoft365
Bots no longer give up on pages that loaded a moment too slowly
A page-load timeout used to mean one thing to the bot: the site is down. On several runs this week, a page that took just over the default five seconds to load was reported as "Website is not available", even though the browser was showing the page perfectly well. The run failed, and the log gave no clue whether the server was slow or the network was blocking the connection.
We changed how the bot handles a timeout. It now checks whether the page actually arrived before deciding the site is unreachable. If the server answered and there is no error page, the bot logs a warning and carries on. If the site genuinely did not respond, it still fails as before.
We also improved the error message for real failures: it now says how long the page had, where that time came from, and whether the server answered at all. For processes that open links from desktop applications, the bot now uses the time set on that step rather than the browser default.
#Automize #BotReliability #DigitalWorkers #Automation