Skip to content

Changelog

Each published version carries its notes, split by audience so everyone reads only what changes for them:

SectionFor whomWhere you see it
Designer and PackagesWhoever designs robotsThe What’s new panel on the Designer start screen shows only these two. If a version changes nothing for designing, it says so.
Platform and AgentWhoever administers Zoan Cloud and the robot machinesThe update notice (which lists everything the version brings) and this page.

Zoan Cloud news that doesn’t depend on installing a version (the portal) is listed separately, by month.

  • Menu by capability: Inicio, Tareas, Centro, Gobierno and Administración (Home, Tasks, Center, Governance, Administration), with shortcuts and Ctrl+K to go to any page, even by its old name. The Centro gathers robots, flows, AI, IDP and resources in tabs, organized by folders. See The Zoan Cloud menu.
  • Tasks with response targets, escalation, reassignment, attachments and metrics; and Governance with AI governance, AI usage and Audit in one place.
  • Folders and access: each area organizes its processes, flows, assistants and documents in folders, and people’s permissions add up.
  • Orchestrations are now called Flujos (Flows) and their instances, Casos (Cases). Your flows, cases and links stay the same.
  • Credentials in folders: each area keeps its credentials and integrations in its folder, shares them with Vincular desde otra carpeta (Link from another folder), and its robots and assistants use the ones in their folder. What you already had stays at the root.
  • Forms: design them once, without code, with sections, columns, tables, attachments, rules, calculations and sensitive data, and use them in flows, assistants and robots.
  • Preview with sample data and Probar envío (Test submission) to confirm Zoan Cloud would accept the answer before publishing.
  • Human Tasks package 1.3.0: Create Human Task uses a form from the library by its name, and the new Download Human Task File downloads the files in the answer.
  • Business error route: the robot’s error travels along the whole route in {{_error…}} and the case shows which way it went.
  • Duration of each case and each step, and Case log: everything that happened on a single timeline.
  • Statistics for each flow and an audit of who designed, operated or viewed a case’s data.
  • Gateways with no se cumple (is not met) and comparison with another case variable.
  • Knowledge bases with [n] citations to the document and page, the Sin fuente (No source) flag, configurable sources in the web chat, plan limits and fair use.

2026-10-03

  • The Designer speaks your language in activities too: names, descriptions, fields and list options appear in Spanish or English depending on the language you choose, and switch instantly. See Language and help.
  • Each activity field shows a clear name with its unit (for example “Timeout (ms)”) and the technical name below it for use in expressions.
  • All 35 activity packages ship their help in Spanish and English; the Package Manager shows names, descriptions and categories in your language.

2026-10-02

  • The data a process returns always reaches Zoan Cloud, also when the robot finishes right while the Agent is reading its last messages.

2026-10-02

  • In the Throw activity you pick the error type from a list: «Technical error» or «Business exception». A business exception reaches Zoan Cloud as «Business error» and is not retried; the canvas card shows it.
  • What’s new shows only what changes when you design robots.
  • Processes that run unattended with a robot session always receive their input data; if it could ever not be read, the run says so with a clear error instead of continuing without it.

2026-10-01

  • Updates are managed by the updater: it checks every 4 hours, lets you know with a Windows notification and, if you don’t install them right away, they install themselves when you’re not using Zoan.
  • After an update, Zoan reopens what it closed also on Windows profiles with accents or spaces in the name.
  • Updates no longer interrupt you: they arrive as a Windows notification and install when you close the Designer; meanwhile the status bar tells you one is ready.
  • The Agent updates between runs without cutting any short, both in the tray and as a service.

2026-10-01

  • Run and Publish no longer let through an undeclared variable hidden behind a warning, nor an assignment to a variable that does not exist.
  • Subplaybooks are checked before running: one missing from the project, an output it does not have, and those invoked with a computed path.
  • If the pre-run check cannot analyze a playbook, it says so and does not let you run or publish.
  • When a run fails, Zoan Cloud receives the error type and the activity that failed, also from an invoked playbook, and the reason when a robot rejects a run.

2026-09-30

  • Zoan Cloud rejects a process that uses an activity missing from the declared version of its package, instead of letting the robot fail at run time.
  • Own OAuth apps (BYOA) are back in the environment Connections, and New connection warns when the provider needs your own app.
  • Live view is only offered on unattended runs of Windows agents, the ones that can be streamed.
  • The headless worker pulls the latest image on every start.
  • Before publishing, the Designer checks with Zoan Cloud that every activity used exists in the published version of its package and, if one is missing, says which one and which version to publish with.

2026-09-29

  • Stop or Terminate an execution: Stop asks the robot to stop when it finishes what it is doing and the execution ends Stopped; Terminate cuts it right away.
  • Templates by kind of work: transactional process, queue dispatcher, sequential and human-in-the-loop processes. They ask nothing at creation: everything is tuned in their Config.xlsx.
  • Queue dispatcher: reads an Excel file or a folder and fills a Zoan Cloud queue without duplicates; running the load again creates no extra items.
  • What’s new shows each version’s notes and the update notice tells what it brings.
  • Stop (⇧F5) asks for a controlled stop and keeps Terminate at hand to cut it right away.
  • Add variable shows the new row right away and switching templates in New project no longer closes the Designer.
  • The last logs of a run from the Designer reach Zoan Cloud complete, and the console keeps each long message in its column.
  • The Designer no longer stores Zoan Cloud responses or the session token in the temp folder.
  • The Agent tray has Stop and Terminate, and an execution terminated from it ends cancelled, not failed.
  • New Should Stop activity to stop at a safe point; Process Queue honors it by itself and Finally still closes what is open when the execution is terminated.

2026-09-29

  • A single update notice for Designer and Agent, installed together with one confirmation.
  • Home screen with project templates; save any project as a template and share it as a .zoantpl file.
  • Project tree with folders, context menus and inline rename; .zoanignore decides what stays out of the package.
  • Variables and arguments are edited inline, Ctrl+Shift+V creates the variable on the fly and bottom panel columns resize.
  • Closing a tab with changes asks whether to save them.
  • New Kill Process and Take Screenshot activities to recover hung applications.
  • Business errors are no longer retried by Retry or Process Queue.
  • Text parameters accept expressions.

Lanzamiento inicial.

  • Multi-tenancy with subdomain resolution
  • Management of environments, agents, processes and executions
  • Triggers manuales y programados (cron)
  • Credential management by environment
  • Roles: Owner, Admin, Developer, Operator, Viewer
  • Real-time execution logs
  • Visual playbook editor with node canvas
  • Searchable Activity Palette
  • Expression engine with autocompletion
  • Local execution from the Designer
  • Invoke Playbook with variable mapping
  • Running in attended and unattended mode
  • Registration with machine key
  • Automatic update from Zoan Cloud
  • Support for multiple environments

Browser, Collections, Core, CSV, Database, DataTable, Desktop, Excel, Filesystem, Google Sheets, HTTP, JSON, OCR, Outlook, PDF, SFTP, SMTP/IMAP, UI, Word, XML, ZIP