Start a project
Menu
ServicesAll servicesCybersecurityCloud EngineeringApplication ServicesEnterprise PlatformsData & AnalyticsAI & Machine LearningInternet of ThingsMobilize Talent
PlatformsAll platformsIdentity and accessPrivileged access and secretsERP, HCM and financeCRM, ITSM and automationHealthcareInsurance and bankingData and integrationCloud and AIIndustrial, utilities and mainframeSkills matrix
Case studiesAll case studiesIdentity and accessPrivileged accessSecurity operationsCloud and infrastructureApplicationsERP and HCMCRM, ITSM and automationIndustry platformsData and analyticsAI and agents
IndustriesAll industriesEnergy, oil & gasHealthcare payersBanking & financial servicesInsurancePublic sectorManufacturingLocations
InsightsField notesLearning tracks
CompanyAbout CohashPortfolioSkills matrixCareersTrust and securityContact
Start a project
automation

Orchestrator and Studio 2024.10 are out of mainstream support. Here's how we get you to 2025.10 LTS.

Orchestrator and Studio 2024.10 left mainstream support on 21 October 2026, and 2023.10 is out of support everywhere. Automation Suite 2024.10 follows on 11 November. We upgrade all three to 2025.10 LTS, convert Windows-Legacy projects, and add agents only where they earn their place.

Talk to a UiPath engineerWhat changed recently
platform dossierUiPathAutomation
Current LTS
2025.10 (Orchestrator, Studio); Automation Suite 2.2510
2024.10 LTS
Mainstream ended 21 Oct 2026; Automation Suite ends 11 Nov 2026
2023.10 LTS
Out of extended support everywhere; Automation Suite ended 3 Nov 2026
Official package feed
pkgs.uipath.com; old Azure DevOps address scheduled for removal April 2027
release watch
  • gemini-3.6-flash removal on 19 November 202619 Nov 2026
  • Coded agents lose their own AI Trust Layer settings2 Dec 2026
connects with
S/4
in short·15-second read

Orchestrator and Studio 2024.10 LTS lost mainstream support on 21 October 2026, and Automation Suite 2024.10 loses it on 11 November 2026, with extended support to 21 October and 11 November 2027.

On 19 November 2026 UiPath removes gemini-3.6-flash; gemini-3.8-flash replaces it. Move to 2025.10 LTS and repoint any bring-your-own model settings first.

you probably need this if
  • Orchestrator still runs 2023.10 or 2024.10, and the October 2026 support dates came and went without an upgrade.
  • Most processes are Windows - Legacy projects and nobody owns the conversion.
  • Robots fail after every SAP or Salesforce release because selectors break.
terms on this page SafedefinitionCyberArk's container for accounts. You add people as safe members, and their rights there decide whether they can list, use or manage what's inside.explained in a field note →LTSdefinitionLong-term support. Databricks fixes stability and security problems in an LTS runtime for three years after release. Other runtimes get six months, which is why an LTS is the one to build on.explained in a field note →Extended SupportdefinitionIBM's paid support once a release's normal support has ended. Security Verify Access 10.0.x moved onto it in April 2026, except on hardware appliances, so check your contract still covers you.explained in a field note →OrchestratordefinitionThink of it as the robots' dispatcher. It holds the schedules, queues and credentials, and tells each robot what to run next.explained in a field note →Automation SuitedefinitionThe version of UiPath you host yourself on Kubernetes or Linux, with Orchestrator and the other services inside it. It has its own support dates, which trail standalone Orchestrator by days or weeks.explained in a field note →
Ask an engineer facts checked 2026-11-05
how it runs
  1. 01Estate inventory
  2. 02Upgrade and conversion plan
  3. 03Rehearse and convert
  4. 04Cut-over and run
you keep
  • A process inventory showing each project's compatibility, its package versions and who owns it, so nobody guesses what an upgrade touches
  • An upgrade path to 2025.10 LTS that follows UiPath's lifecycle dates, so nothing sits past its support end
  • A plan for converting the Windows - Legacy projects in waves, with a regression test for every process before it moves
+ 3 more documents
who does it
UiPath RPA developer (Studio, REFramework)UiPath solution architectUiPath Automation Suite infrastructure engineer Automation Developer Associate Automation Developer Professional
platforms
S/4
proof
1 case study on this
background
2023.10 out Suite 2023.10out Upgrade to2025.10 2024.10 out Oct 2026 Nov 2027
field note · 14 minUiPath 2023.10 support has run out and 2024.10 is next. What we'd upgrade first
uipath · release timeline
  1. 30 Apr 2025 UiPath Maestro GA Maestro went GA the day UiPath launched its agentic automation platform. UiPath calls it the orchestration layer at the heart of that platform, so that's where we'd start any agent work in an existing estate.
  2. 12 Oct 2026 Windows 10 and Server 2019 Robot VM images deprecated If your cloud robot pools still boot Windows 10 or Windows Server 2019, they're on images UiPath deprecated on 12 October 2026. You can keep creating pools on them until 31 January 2027, and existing pools are supported until 30 April 2027. Move server pools to Windows Server 2025 and desktop pools to Windows 11 Enterprise, and test the processes that drive desktop apps first.
  3. Oct 2026 Studio, Robot and Assistant move to the Platform Installer Starting with 2026.10, Studio, Robot and Assistant come through the UiPath Platform Installer. Orchestrator's Auto Update policies only cover clients older than 2026.10, so once machines reach that version those policies won't touch them. Set up governance policies to manage updates before the first machines get there.
  4. Oct 2026 No standalone Test Manager 2026.10 Standalone Test Manager stops at 2025.10. UiPath isn't shipping a 2026.10 version, so anyone running it themselves ends up on Test Cloud eventually. UiPath's platform and artifact migration steps cover the move, and it's easier to start while 2025.10 is still supported.
  5. 21 Oct 2026 2024.10 LTS mainstream support ended Orchestrator, Studio and Robot 2024.10 dropped out of mainstream support on 21 October 2026. Extended support still runs until 21 October 2027, which buys you a year. Use it to plan the move to 2025.10 LTS properly, because a rushed upgrade in late 2027 is how processes break in production.
  6. 23 Oct 2026 Generate Text Completion activity removed On 19 October 2026 UiPath pulled the Generate Text Completion activity from the OpenAI and Azure OpenAI connectors. OpenAI workflows that still call it fail after 23 October 2026. So if a job started failing in late October and nobody changed anything, look for this activity first. The fix is to swap in Generate Chat Completion and retest the prompt.
  7. 25 Oct 2026 2023.10 LTS extended support ended Standalone Orchestrator 2023.10 and Test Manager 2023.10 lost extended support on 23 October 2026, and Studio and Robot followed two days later, on 25 October. Automation Suite 2023.10 was the last to go, on 3 November 2026. If you're still on 2023.10 anywhere, you're running unsupported software and the upgrade belongs at the top of the list.
  8. today · Nov 09, 2026
  9. 11 Nov 2026ahead Automation Suite support dates Automation Suite trails standalone Orchestrator by a few weeks. Extended support for 2023.10 ended on 3 November 2026, so any cluster still on it is unsupported now. On 2024.10 mainstream support stops on 11 November 2026 and extended support still runs until 11 November 2027. The target is 2025.10, listed by UiPath as 2.2510.
  10. 19 Nov 2026ahead gemini-3.6-flash removal on 19 November 2026 Google retires gemini-3.6-flash on 19 November 2026 and UiPath takes it out of the whole platform the same day. Today it sits behind Autopilot, Delegate and Cartographer. On UiPath-managed models you get moved to gemini-3.8-flash without doing anything, but run your own tests on it first. Bring-your-own setups are different. A configuration that still names gemini-3.6-flash becomes invalid, and UiPath falls back to its managed models unless you've repointed it.
  11. 1 Dec 2026ahead Process Mining leaves Automation Cloud Public Sector Process Mining is leaving Automation Cloud Public Sector, and after 1 December 2026 it won't be there at all. UiPath still offers it through its other delivery options. If you use it on Public Sector, pick one of those soon, because a move like that rarely fits in the last week.
  12. 2 Dec 2026ahead Coded agents lose their own AI Trust Layer settings On 2 December 2026 UiPath drops the separate AI Trust Layer settings for coded agents in Automation Cloud and Test Cloud. After that, coded agents follow whatever you configured for low-code agents. Anything set only on the coded side is ignored. Automation Ops changes the same way. One agents policy covers both, and the Enable Coded Agents toggle disappears. If your coded agents use an LLM configuration that low-code agents don't, move it across before the 2nd.
  13. Apr 2027ahead Official package feed moves to pkgs.uipath.com UiPath is moving its official package feed off pkgs.dev.azure.com to pkgs.uipath.com/official/index.json, and the old address is scheduled to go away in April 2027. After that, an Orchestrator host Libraries feed still pointing at it can't download official packages. Add pkgs.uipath.com to your outbound allowlist and look for the old URL in machine images and unattended installs, and in tenant settings too. Studio 2026.0.199 and later rewrite it on upgrade. On 2024.10 and 2025.10 you add the new feed by hand, until a future patch does it for you.
  14. no date yetWindows - Legacy projects in Studio STSStudio STS won't create or edit Windows - Legacy projects any more. Studio LTS still can, and will for the foreseeable future.
the story · uipath estate

From the first call to a setup your own team can run.

Here's what usually prompts a call about your UiPath estate, what we do about it and in which order, and where you end up.

  1. chapter 01 · where it hurts

    Why teams reach out

    • Orchestrator still runs 2023.10 or 2024.10, and the October 2026 support dates came and went without an upgrade.
    • Most processes are Windows - Legacy projects and nobody owns the conversion.
    • Robots fail after every SAP or Salesforce release because selectors break.
  2. chapter 02 · what we change

    How we solve it

    • Orchestrator and Automation Suite upgrades
    • Windows-Legacy project conversion
    • Automation Cloud migration
    • Agentic automation with Maestro
    • Robot security and credentials
    • Run support
  3. chapter 03 · how it runs

    Our approach

    • Estate inventory
    • Upgrade and conversion plan
    • Rehearse and convert
    • Cut-over and run
  4. chapter 04 · where you end up

    What changes

    • Orchestrator gets back onto a supported release quickly.
    • The AP team now checks the agent's proposals instead of working each exception from nothing.
    • A process inventory showing each project's compatibility, its package versions and who owns it, so nobody guesses what an upgrade touches
    • An upgrade path to 2025.10 LTS that follows UiPath's lifecycle dates, so nothing sits past its support end
what we do

Our UiPath work

6 kinds of UiPath work, each run by engineers who have done it on live tenants.

  1. Standalone Orchestrator or Automation Suite moved to the 2025.10 LTS line, with database backups, tenant settings, queues and assets checked before and after.

  2. Projects converted from Windows - Legacy to the Windows compatibility, activity packages updated and each process regression-tested against the target applications.

  3. On-premises Orchestrator tenants moved to Automation Cloud, with robots, folders, credentials and schedules mapped and cut over by process group.

  4. Long-running processes modeled in UiPath Maestro, with agents, robots and people each doing the steps they are suited to, and human approvals where the risk calls for it.

  5. Robot accounts, credential stores and Orchestrator roles reviewed so unattended robots hold only the access their processes need.

  6. Queue monitoring, failed job triage, and a fix list for the processes that break every time a target application changes.

capability 01 / 06in production

Orchestrator and Automation Suite upgrades

Standalone Orchestrator or Automation Suite moved to the 2025.10 LTS line, with database backups, tenant settings, queues and assets checked before and after.

talk to an engineer about this →
capability 02 / 06in production

Windows-Legacy project conversion

Projects converted from Windows - Legacy to the Windows compatibility, activity packages updated and each process regression-tested against the target applications.

talk to an engineer about this →
capability 03 / 06in production

Automation Cloud migration

On-premises Orchestrator tenants moved to Automation Cloud, with robots, folders, credentials and schedules mapped and cut over by process group.

talk to an engineer about this →
capability 04 / 06in production

Agentic automation with Maestro

Long-running processes modeled in UiPath Maestro, with agents, robots and people each doing the steps they are suited to, and human approvals where the risk calls for it.

talk to an engineer about this →
capability 05 / 06in production

Robot security and credentials

Robot accounts, credential stores and Orchestrator roles reviewed so unattended robots hold only the access their processes need.

talk to an engineer about this →
capability 06 / 06in production

Run support

Queue monitoring, failed job triage, and a fix list for the processes that break every time a target application changes.

talk to an engineer about this →
typical situations

UiPath situations we walk into

We pieced these together from UiPath situations that come up a lot. They're patterns. You won't find a specific client in them.

case file 01

Orchestrator 2023.10, 400 Windows - Legacy processes, extended support already over

composite · not a client story
  1. Beforethe situation

    Standalone Orchestrator is on 2023.10, and its extended support ended on 23 October 2026. Most of the 400 processes are Windows - Legacy projects on old activity packages. The CoE has two developers to deal with all of it.

  2. What we dothe work

    We rank processes by business impact, move Orchestrator to 2025.10 LTS first, since Studio LTS still edits Windows - Legacy projects, then convert processes in waves with a regression test for each.

  3. Afterwhere you end up

    Orchestrator gets back onto a supported release quickly. After that, converting projects is planned work done in waves, and it stops being an emergency.

case file 02

Invoice exceptions fixed by hand while the robot next to them works fine

composite · not a client story
  1. Beforethe situation

    A robot posts invoices into SAP. A third of them fail on mismatched purchase order lines, and those end up in a shared mailbox where the AP team fixes them by hand.

  2. What we dothe work

    Past exceptions come first, as an evaluation set. Then we model the process in Maestro and add an agent step that reads the invoice and the PO, proposes a match and explains why. Low-confidence cases go to an AP approver to decide.

  3. Afterwhere you end up

    The AP team now checks the agent's proposals instead of working each exception from nothing. The evaluation set was built first, so you've seen how the agent behaves before it goes near production.

case studies

UiPath case studies

All case studies
AI rollout AI and agents

Classic RPA bots to agentic automation

Moving classic RPA bots to agentic automation in UiPath or Power Automate. APIs first, agents only where judgment is needed, and controls on both.

read the case study
approach

How a UiPath engagement runs

We don't start a step until the last one has produced something you can check.

  1. step 01

    Estate inventory

    We list the Orchestrator, Automation Suite and Studio versions you actually run, and which processes sit on which project compatibility. Then we add the activity package versions, the robot accounts and the target applications each process touches.

  2. step 02

    Upgrade and conversion plan

    We map the version path to 2025.10 LTS and decide which Windows - Legacy projects convert first. Then we build regression tests for the processes the business can't run without, so every wave has something to pass.

  3. step 03

    Rehearse and convert

    We upgrade a non-production Orchestrator, convert and test processes in waves, and fix selectors and package conflicts as they surface.

  4. step 04

    Cut-over and run

    We upgrade production in a planned window, reconnect the robots and keep an eye on them. Then your CoE gets the queue dashboards and runbooks.

ai on uipath

Where AI fits on UiPath, and where it needs guardrails.

The UiPath Platform is what UiPath sells for agentic automation. Its Maestro, GA since April 2025, coordinates agents, robots and people across long-running processes. Orchestrator hosts and connects MCP servers too. Agents handle the judgement steps robots can't, and in return they need test sets, approval points and narrowly scoped service accounts.

AI agentasks for data or an action
Scoped identityonly the access it needs
MCP serverthe one door into the platform
Logged, approveda person signs off on writes
UiPathdoes the work

Orchestrator has MCP support built in. It covers UiPath, remote, command, coded and self-hosted servers, with Platform and Swagger types still in preview. We run every server under a robot account scoped to its folder and we log its tool calls. A write to any business system has to pass a Maestro approval step first.

UiPath Maestro

Maestro models long-running processes where agents, robots and people each take steps. We put agents on exception handling first, reading documents or triaging cases, say. A person keeps approving actions on live transactions.

MCP servers in Orchestrator

In Orchestrator you can expose UiPath processes as MCP tools and connect remote, coded or self-hosted MCP servers. Two server types, Platform and Swagger, are in preview. We publish only the processes an agent needs. For external servers we stick to trusted providers.

Agent evaluation before production

Agents make probabilistic decisions. So we build a test set out of real past cases and agree the pass criteria with the process owner, and we rerun it after each prompt or model change.

AI help with Windows - Legacy projects

Studio STS no longer edits Windows - Legacy projects. An AI assistant can document old workflows and draft conversion notes. Developers still rebuild and test each one.

architecture

From a ServiceNow ticket to an SAP posting, and where UiPath does the work in between

Follow an invoice email. It becomes a queue item in Orchestrator, which hands it to an unattended robot, and the robot keys it into SAP through the screens. A ServiceNow request takes the longer route through Maestro, where judgement steps go to an agent that calls a language model and the routine steps go back to Orchestrator as robot jobs.

From a ServiceNow ticket to an SAP posting, and where UiPath does the work in between Follow an invoice email. It becomes a queue item in Orchestrator, which hands it to an unattended robot, and the robot keys it into SAP through the screens. A ServiceNow request takes the longer route through Maestro, where judgement steps go to an agent that calls a language model and the routine steps go back to Orchestrator as robot jobs. 01 · TRIGGERS 02 · UIPATH PLATFORM 03 · EXECUTION 04 · BUSINESS SYSTEMS start process queue items judgement step robot job model call dispatch UI automation API calls SE ServiceNow requests · tickets Email and documents invoices · forms UiPath Maestro process orchestration UI Orchestrator2025.10 queues · assets ·schedules Agents document reading · triage Unattended robots Windows VMs · AutomationSuite AI Language model via approved AIprovider S/4 SAP GUI · Fiori Sf Salesforce cases · accounts © Cohash · cohash.com
01 · TRIGGERS02 · UIPATH PLATFORM03 · EXECUTION04 · BUSINESS SYSTEMS ServiceNow: requests · tickets ServiceNow requests · tickets Email and documents: invoices · forms Email anddocuments invoices · forms UiPath Maestro: process orchestration UiPathMaestro processorchestration Orchestrator 2025.10: queues · assets · schedules Orchestrator2025.10 queues · assets· schedules Agents: document reading · triage Agents documentreading ·triage Unattended robots: Windows VMs · Automation Suite Unattendedrobots Windows VMs ·Automation Suite Language model: via approved AI provider Language model via approved AIprovider SAP: GUI · Fiori S/4 SAP GUI · Fiori Salesforce: cases · accounts Salesforce cases · accounts start process queue items model call dispatch UI automation API calls © Cohash · cohash.com
use cases

Typical UiPath projects

The work teams usually bring us, and the platforms UiPath has to talk to while we do it.

  1. UIP-01 Orchestrator is past its October 2026 support dates on 2023.10 or 2024.10, and nobody has booked the upgrade common request
  2. UIP-02 Hundreds of processes are still Windows - Legacy projects common request
  3. UIP-03 Robots break whenever a target application changes a screen, and someone patches the selectors by hand again common request
  4. UIP-04 Your robots still pull from the old Azure DevOps package feed, or your allowlist doesn't include pkgs.uipath.com common request
  5. UIP-05 Someone wants on-premises Orchestrator moved to Automation Cloud and the upgrades off your team's plate common request
  6. UIP-06 Leadership wants agents in production and the team needs a safe first use case common request
UiPath · connected platforms
ServiceNowSalesforceSAP S/4HANAMicrosoft Dynamics 365Microsoft Entra IDOpenAI API
you keep

What a UiPath engagement leaves behind

These are working documents, written against your configuration, so your team can run them without us.

  • inventory01

    A process inventory showing each project's compatibility, its package versions and who owns it, so nobody guesses what an upgrade touches

    yours to keep
  • document02

    An upgrade path to 2025.10 LTS that follows UiPath's lifecycle dates, so nothing sits past its support end

    yours to keep
  • tests03

    A plan for converting the Windows - Legacy projects in waves, with a regression test for every process before it moves

    yours to keep
  • document04

    Least-privilege changes for robot accounts and credentials, worked out from what each process actually touches

    yours to keep
  • runbook05

    Orchestrator upgrade runbook with rollback steps

    yours to keep
  • document06

    A brief for the first agent: the use case, how we'll judge it, and where a person approves

    yours to keep
talent and delivery · uipath

Certified engineers, wherever you need them.

Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.

Onsite

Engineers at your sites in the US

Nearshore

Overlapping hours with US teams

Offshore

Overnight progress on your backlog

All time zones

Coverage handed over across time zones

24-hour coverage · US Central time
OnsiteUS business hours
Nearshoreoverlapping US hours
Offshoreovernight progress
Combinedhandover, not hand-off
certifications our engineers hold
  • Automation Developer AssociateUiPath
  • Automation Developer ProfessionalUiPath
  • Agentic Automation AssociateUiPath
  • Infrastructure Engineer Professional – Automation SuiteUiPath
roles we staff
  • UiPath RPA developer (Studio, REFramework)
  • UiPath solution architect
  • UiPath Automation Suite infrastructure engineer
  • UiPath developer who builds agents and Maestro processes
  • Automation CoE lead
due diligence · uipath

Questions to ask any partner, including us.

Put these to anyone bidding on your UiPath work. The ones who've done it answer differently from the ones who've read about it.

  1. Q1

    Going by UiPath's own lifecycle page, which of our components are already out of support or close to it?

    Orchestrator, Studio and Automation Suite each have their own dates. Build the plan around one date and you'll miss the others.

  2. Q2

    After converting the Windows - Legacy projects, how are you going to regression-test our processes?

    Conversion changes activity packages and runtime. Without a test per process, failures show up in production queues.

  3. Q3

    What would you change about how our robots log in and where their credentials live?

    Unattended robots often run on broad service accounts. That's an audit and security problem well before anyone starts on agents.

  4. Q4

    What will you test an agent against before it touches a live transaction, and who signs off?

    An agent's decisions are probabilistic. Before it goes to production you want, at a minimum, a test set built from real past cases and a threshold below which a person approves.

  5. Q5

    If we move Orchestrator to Automation Cloud, what's still ours to run on premises?

    The robots stay your problem, and so does their network path to the target systems. Ask to see where each robot will run and how it reaches its applications before you sign.

01Which UiPath versions are still supported?

Go by the line you're on. 2025.10 is the LTS for Orchestrator and Studio, in mainstream support to late October 2027. 2024.10 has extended support until 21 October 2027 (11 November for Automation Suite). 2023.10 has run out everywhere, Automation Suite included since 3 November 2026, so anything still on it goes first.

02When does UiPath 2024.10 end of support hit?

Mainstream support for Orchestrator and Studio 2024.10 ended on 21 October 2026, and extended support for both runs until 21 October 2027. Automation Suite 2024.10 is a few weeks behind, leaving mainstream on 11 November 2026 with extended support to 11 November 2027. Plan the 2025.10 upgrade early in that year, not at the end of it.

03Do we have to convert Windows - Legacy projects?

Not immediately if you stay on Studio LTS, which still edits them. Studio STS no longer creates or edits them, and new projects default to Windows. Most teams convert as part of an upgrade so they aren't tied to one Studio track.

04How long does an Orchestrator upgrade take?

The platform upgrade is the quick part. Most of the time goes on regression-testing your processes, particularly anything built as a Windows - Legacy project or on old activity packages. We size the job from your process inventory.

05UiPath is removing gemini-3.6-flash. What do we have to change?

It goes on 19 November 2026. Autopilot, Delegate and Cartographer use it now, and on UiPath-managed models UiPath switches them to gemini-3.8-flash for you. Your job is testing that the outputs still hold up. If you bring your own model and point at gemini-3.6-flash, change the setting first, or UiPath falls back to its managed models.

06Where do agents fit in our UiPath estate?

Look at the exceptions your people already clear by reading a document or an email. Those are the steps Maestro can hand to an agent, with a person approving the result. The robots keep doing the rule-based work.

07Do you staff UiPath developers?

Yes, on contract, contract-to-hire or permanent terms. We place UiPath developers and solution architects, and infrastructure engineers as well. Some work onsite in the US and others nearshore or offshore, so any time zone is covered.

services

Related services

Projects on UiPath usually end up touching one of these, so they're worth a look.

you are hereUiPath
fact-checked Checked against vendor and official documentation last checked 2026-11-05 content fingerprint ad1ba2cc
  1. 01Book a 30-minute working sessionsenior engineer
  2. 02Talk to an engineer about your setupreply within 24 hours
  3. 03See how similar projects wentcase studies
Reviewed by the Cohash team UiPath is a trademark of its owner, used here to identify the platform. how we handle facts and data →
next step

Tell us what you're running. We'll tell you what we'd do first.

A 30-minute working session with a senior engineer. No slides.

Book a working session See the case studies
useful to bring
  • The platform and the version you're on
  • Where you need to get to, and by when
  • What's custom: rules, plugins, integrations
  • Any audit finding or deadline driving it