Workflows V1 Deprecation
Workflows V1 was removed on September 7, 2026. Unmigrated V1 workflows no longer run. If you still need to move a V1 workflow to V2, use the migration tool.
Overview
| Feature | Workflows V1 |
| Affected component | Enterprise Knowledge (EKB) |
| Status | Removed |
| Removal date | September 7, 2026 |
| Replacement | Workflows V2 |
What changed
Workflows V1 was the original workflow builder in EKB. It was deprecated after the launch of Workflows V2 in September 2025, which introduced a redesigned interface, improved performance, and expanded capabilities for building agentic automation workflows.
Workflows V1 was removed on September 7, 2026. Unmigrated V1 workflows no longer function. Use the migration tool if you still have V1 definitions to move to V2.
Timeline
- Announcement — Completed
Workflows V1 was announced for deprecation. Existing workflows continued to run normally with no changes required at announcement time.
- June 1, 2026 — Migration tool available (v2.1.0)
The migration tool became available in the platform. A call-to-action (CTA) in the Workflows V1 interface allowed migrating existing workflows to V2 in place — without rebuilding them manually.
- September 7, 2026 — Removal (completed)
On September 7, 2026, Workflows V1 was removed from EKB. Any workflow that had not been migrated to V2 stopped functioning.
The in-platform migration tool has been available since June 1, 2026 (v2.1.0). Use it if you still need to migrate remaining V1 workflows to V2.
Impact
Workflows that were still on V1 after September 7, 2026 no longer run. Agents or automations that depended on those workflows are affected until they point at a migrated V2 workflow.
The Migrate Flow tool remains available for moving remaining V1 workflow definitions to V2. See the migration guide.
Any workflow that was still on V1 after the removal date no longer functions. Migrate to V2 and update callers to the new workflow.
Why this change was made
Workflows V2 (Workflow Builder v2) launched in EKB v1.7.0 and is the current workflow builder. It replaced the original interface with a more intuitive, visual builder while expanding what's possible for agentic automation.
A redesigned drag-and-drop canvas makes it easier to build, connect, and configure workflow components without navigating complex menus.
Workflows V2 supports four trigger types: Manual Input, File Upload, Schedule, and Email — enabling a wider range of automation scenarios.
Drag Agents, Tools, Conditions, and Final Outputs directly onto the canvas and link them visually to build multi-step agentic workflows.
Pass data between steps using the @ symbol to reference variables, enabling dynamic, connected workflows across components.
The Executions log lets you inspect every step of a past run — inputs, outputs, and results — making it easier to identify and fix failures.
Every published workflow saves a version history. You can view previous versions and restore and republish an earlier version at any time.
For a full walkthrough of Workflows V2, see the Workflow Builder v2 documentation.
Frequently asked questions
Does Workflows V2 support everything V1 did?
Workflows V2 covers all the actively used toolkits and nodes of V1 use cases. If your workflow relied on a toolkit or feature that is not available on V2, reach out to your Account or Engagement Manager for further assistance.
Do I need to do anything now?
If you already migrated before September 7, 2026, no further action is required for the V1 removal. If you still have V1 definitions or callers pointing at V1, use the migration tool, publish the V2 workflow, and update agents or integrations to the V2 endpoint.
Were workflows automatically migrated?
No. Migration was not automatic. A CTA in the Workflows V1 interface let you migrate each workflow to V2 in place. You had to trigger the migration and verify the result.
What happened if I did not migrate before the removal date?
Any workflow still on V1 after September 7, 2026 stopped functioning. Agents or automations that depended on those workflows were affected. Use the migration tool if definitions remain, then update callers to V2.
Does migration preserve my workflow configuration?
The in-platform migration tool is designed to carry over your existing workflow configuration to V2. After migration, review the workflow in V2 to confirm all steps, triggers, and settings carried over correctly.
Can I still use V1?
No. Workflows V1 was removed on September 7, 2026. Build and run workflows in Workflows V2. Contact your Automation Anywhere account manager if you need migration assistance.
Support
For questions about this deprecation or migration assistance, contact your Automation Anywhere account manager or open a support ticket through the Automation Anywhere support portal.
View announced and completed feature deprecations.