I have found that one or two times out of ten, UiPath Studio hangs and needs to be restarted. These types of technical glitches do happen but not often.

I have not had any issues. If something happened, it happened because of the human network.

It is stable. We are using the 2019 version. The versions are continually upgraded with the latest being the 2021 version. There are frequent updates but the version we are using is stable. We don't have any errors or bot crashes or other unexpected system exceptions during development. The stability is good across all versions.

UiPath is stable.

There are no issues with the stability.

UiPath is always uploading new versions of its software. So far, we haven't had any problems related to UiPath crashing or anything like that. The stability has been satisfactory. It's good, decently stable software.

The solution does crash sometimes. 

In one instance, I was trying to read a file, and the file itself was a bit larger. It's hard to read a large number of files.

UiPath is stable. 

The solution is stable. There is no lagging application-wise. There might be unexpected pop-ups or Windows upgrades that may affect UiPath, otherwise, it is very reliable. 

The stability depends on the client's infrastructure. We're using a Citrix environment and internal infrastructure security has a lot of parameters. It totally depends. Every client has different challenges.

The stability of UiPath is very high, and this is a very important point. In fact, stability was the problem that we had when we were assessing the competition with UiPath. We evaluated several RPA tools and moved on with the UiPath partnership because it was the most robust. It is important to remember that we have a high availability environment, and the entirety of it must be stable. Our team is tool agnostic and extremely skilled in the largest RPA tool providers, enabling us to develop automation on any platform.

UiPath is not 100 percent stable but it is within acceptable range.

Overall, it is very stable. There is low technical debt and monitoring. After a process has been deployed, for the most part, it is stable after testing and everything.

The stability of UiPath really depends on who builds the automation. 

However, the latest version releases, such as 2023.4.4, have been known to contain bugs. For example, we recently upgraded to 2023.4.4 and faced a lot of studio bugs, which forced us to downgrade to 2023.4.2. 

The upgrades on other orchestrators were fine, but there was a bit of a change to the UI that took some time to get used to.

Upon their version releases, there should be a bit more due diligence before they are pushed to customers because almost every time we're given the opportunity to upgrade, there are issues where we have to scale back, wait a while, and then upgrade again.

UiPath is stable.

Previously, we haven't noticed stability issues. In the past year, we have noted issues with stability. There have been some hiccups. 

We've had outages once or twice. For that, they have a workaround. If a server goes down, we should have a backup server for it. If that's the case, it is just a few steps needed to migrate or we can take the setup from another server. That's it. It's pretty good in general. 

UiPath is stable.

It is a stable product. There were some issues while interacting with different applications. For example, with Microsoft, we have issues with One Drive. When UiPath is working on a file, it cannot quickly get to the file. We need to move the file to a local drive before processing the data. Microsoft applications seem to give it trouble. 

I have been using UiPath on a different powerful system that has high-end RAM. Sometimes, it crashes due to the use of multiple components at once. For example, when I was using Druid with data service and another UiPath product. Developing was quite easy. However, when debugging, sometimes it would freeze. I don't know whether it was because of my system and its compatibility, my system's configuration, or the fact that we were using so many high-end tools and products at once. 

The robustness of the tool, when it comes to using high-end products, is something that I am currently exploring. This is something that is currently a bit of concern for other developers as well. I have been interacting with a lot of developers around the globe. As a part of that, I tend to share my experiences. They have shared that it will sometimes freeze, even with simple automation. Because we are using new features or products all at once, it freezes. I think this should not be the case. If you are using long, heavy code, and it gets frozen at one point, I can understand that. However, 10 simple lines of code, while using three or four products at once, is getting frozen. That should be taken care of or improved.

To troubleshoot the system crashing, we contacted UiPath. They were kind enough to reply and have a discussion. They are working on this and trying to make it more convenient so future releases will solve this problem.

It is stable. I would rate it an eight out of ten for stability.

The solution is stable for the most part. I'd rate it eight out of ten. Most of the time, it's working fine. However, sometimes we have small problems with the data connection or pushing data. It can be difficult to identify the orchestrated things. 

UiPath is stable. 

Stability-wise, we haven't really found any issues lately.

In the earlier versions, from 2016 and 2017, there were some issues that were never resolved by the UiPath team. The newer versions, especially while performing web scraping, are much more stable. Once it was deployed, we haven't seen any issues with the .NET applications.

Instability in our use case is the result of the target system; for example, the one that is operated by Universal Studios. If they are unresponsive for perhaps 20 or 30 seconds and the robot is expecting to see a certain screen, especially when it normally only takes two or three seconds to move from one screen to the other after submitting a request, it is going to cause a problem. However, that's not the fault of UiPath or RPA in general, but a fault of the source or target system.

I estimate that with all things considered, UiPath is 99.9% stable.

I would rate the stability as a four (out of five), but some of it could have been us too. 

An overabundance of logging that we created crashed the SQL Server. We had to adjust and restructure the way we were doing all of our logging to prevent that from happening again. Ever since then, it has pretty much been fine. 

We have had issues with upgrades. However, from a normal day-to-day functionality perspective, it is pretty stable.

We have not experienced any crashes of UiPath. We have experienced some slowdowns three times this year, but this could be due to our internal network rather than UiPath.

It is completely stable. I have not had a single downtime in our development journey and usage. It is a very stable solution. I would rate it a ten out of ten in terms of stability.

We never have issues with UiPath's stability. While we have had issues with older versions, the tool continues to improve and it's in great shape now. 

UiPath is generally stable, but there are bugs in UiPath Studio that require fixing or restarting the application.

A few years ago, UiPath wasn't stable, but it matured a lot since then. 

UiPath is a very stable application. We haven't faced any hiccups or any major downtimes. Being a cloud platform, it's very good. The only thing that we need to take care of is our internet and our system. Apart from that, I haven't faced any downtime issues or performance issues with UiPath. 

The stability is great. I compare it to what I would think the best in class is. It's like Microsoft releasing patches. I've had fewer issues with UiPath updates than I do with my Office client on my computer. Therefore, it's very stable. 

We've had it where we had an update, and it did break some of our robots, and we had to go and do some troubleshooting, yet that's only been one time. It's pretty good overall. 

So far, so good. In terms of stability, there are no issues or concerns.

The solution is stable with no problems. 

It is stable. They are updating things, but it is stable with the previous code.

It offers good stability features with minor bugs from time to time.

It offers a great amount of stability, and the team at UiPath is adding more and more features that are increasing the stability of the platform.

The solution is very stable and good. 

UiPath is a stable solution.

I've been pretty impressed with the stability. We've had a couple of minor issues that our developers helped us figure out. It's programming and nobody on my team are programmers. Some of it could be just user error, however, overall it seems like a very stable platform.

The product is quite stable now. There are certainly some places where UiPath has to work, specifically in terms of actual stability, where there are still some unknown errors that are coming in. 

In terms of Orchestrator, I have noticed there are some places where there are glitches. Things are not very clear at first as everything is changing quite quickly, I'll say that. Even in the enterprise version, everyone wants to be on the very latest version. However, there is a drastic change between the versions themselves.

For example, 2019, 2020, and 2021 versions, all three are drastically different amongst themselves. This kind of change is definitely good for the provider in that they are doing something better. However, as a consumer, I don't really want to go ahead and go through an entire learning curve all over again along with handling my current job of handling all the work, just so that I can cope up with what changes the product team has made. It should not be necessary to go through this level of adjustment for each and every release. At this point, I have been through three to four migrations and in each migration, I have gone through some kind of a learning curve.

For the on-premises solution, if we ignore any problems that may occur with the infrastructure, such as the network, then stability is very good and the platform works well.

In my experience with cloud-based deployment, I haven't faced any problems with stability.

We haven't had instability issues.

UiPath is stable. 

We have occasionally observed some abnormalities, but we have not yet found the cause. For one of the processes, we are running macros and triggering them with UiPath. These macros can take ten to eleven hours to run. Sometimes, UiPath stops while a macro is still running. Once the macro is completed, UiPath is supposed to perform another task, but the macro takes so long to run that this does not happen. I believe this is a problem with our program, as it is taking too long to complete. These kinds of delays can occur, and that is understandable.

UiPath is stable.

The solution is stable and services 40% of enterprise customers with no issues. We feel we are in good hands with the solution. 

From a system perspective, it's stable on my end. It just works. That's the best part about it. It just works.

I am very happy with the stability of it. 

I wish that there might be a better, easier method of updating our platform, especially for on-prem. I believe most of their customers are cloud-based. So, they don't have to worry about updating their Studio versions or Orchestrator. Being on-prem, it can be difficult because we must reach out to have that version. We can't just plan on our own. We are always at least a six-month step back versus the current version.

I'm impressed with the version that we have today. 2019.10 is a version that is quite stable, compared to how we did with 2018. A lot of pieces that are enabled as part of the new version, 2019, are stabilized. We have zero downtime with the tool.

The stability is good, but when we migrate to a newer version a few issues can emerge. We just have to do our best and make sure everything is up and running. Overall, the stability is okay.

The stability has been good so far. 

I would rate the product's stability as three and a half, based on our experience. This relates directly back to where we've had challenges. Some of the integration with more mainstream products, like Excel, for example, has been questionable at times. It's just striking that balance between the fact that we want it to be democratized and easy to use by everyone, while we don't want to be in a position where we're forced out of the route to use macros necessarily within Excel. We want the UiPath software to be just as quick and easy to use as that more technical solution. Otherwise, we lose the benefit of having it. It shouldn't be technically inhibited.

I have no issues with stability. UiPath improves how the infrastructure works and how stable everything is. I haven't had many problems. There are a couple of quirks that different product levels will address or resolve, but it's documented pretty well on the support side.

Overall, UiPath is stable for most processes, but Power Automate is better at handling large, complex projects.

The solution is stable.

The solution is stable; we didn't have any downtime outside of updating our environment. 

Stability-wise, I would say, for an ERP, UiPath is good. If you are going to automate some websites, the stability is very bad, however, for ERP it is really good. 

In terms of stability, it's really good. I haven't come across any problems.

We have had some issues with the Community version, but in the licensed version, we have not had any issues. I would rate it a nine out of ten in terms of stability.

There are some performance issues during development. When we transfer a process from one machine to another using GitHub, it will work fine on my machine, but it will take time for the other developers to redownload the particular dependencies. It is not going to update immediately. 

The stability depends on the VM you're running UiPath on, so that's not even really UiPath at that point.

UiPath is a stable product, but there are still some areas where it could improve. 

The solution is very stable. 

The selectors and modern UI are not stable yet. 

UiPath is a stable tool.

The tool has some bugs, and it doesn’t respond sometimes. However, it’s no more unstable than Windows. It is fairly stable.

In general, UiPath is a stable platform. However, the performance tends to slow down frequently after updates.

The stability is very good. It's a 10 out of 10 for reliability.

The stability is good. I did not encounter any issues with UiPath.

When new bots are developed, we definitely see some errors in the first few days, which are usually connector issues. Once the bot is moved to production and has a lot of enhancements and patches to the automations, we make sure that the automation is running smoothly. So, during the initial stages, it won't be very stable, but after a few enhancements to adjust to the automation as time goes, then it will become stable.

Once we deploy and release the automation into production, we will monitor production to see if there are any new challenges, different scenarios, or bugs that we need to fix. We have monitored the automation after deployment for around six to seven months, and the automation went smoothly without any issues. Because the automation is performing pretty well, we have deployed it to more of our workforce and their different jobs.

I would rate the stability of UiPath ten out of ten.

There are still some stability issues. There are sometimes issues related to bots acting up. It can be hard to tell whether that is something related to how we developed it or whether the bots are having an issue. We are not sure why, but there are some stability issues.

I would rate its stability capabilities nine out of ten as there is always room for improvement.

Compared to Automation Anywhere or other open-source tools, UiPath's stability is very good. However, when it comes to very complex hybrid automation with high-density bots, where we require many third-party applications, UiPath cannot handle such scenarios.

PDF automation is very complex. Either we will have to use a third-party Python script, or we will have to build a custom OCR. We require good programming knowledge. The product must improve its stability. I don't see much stability. Though it is available in an environment like Mac, it is not up to the mark as it is in Windows.

It is a stable environment. It doesn't encounter any errors on its own, unless there are system or functional exceptions.

The stability of UiPath is better than Automation Anywhere.

It's stable.

The stability is awesome. It is very stable. It recovers itself. It doesn't err. It's very easy to carry on, and exception handling is very easy to manage it. I have no problem with it.

The stability has been good so far but we do not have much volume. We handle diverse implementations that include five to ten bots. We do not yet have the load to fully rate performance. 

This is a stable solution. The bots in the system are stable and function according to their instructions. They only stop when they encounter a new scenario they have not dealt with before. 

The product is great. It's very stable. It's reliable. We trust it with a lot of different and very important automations. If UiPath wasn't stable, it would introduce quite significant operational risks to the firm.

With the help of all the dynamic options in UiPath, the stability of the bots has been very good.

We have run into issues with integration services where we developed something, implemented it, put it into production, and all of a sudden, it does not run unattended. It is a very frustrating situation to be in. 

There were some issues with sharing connections between different accounts, and we have learned from that experience to do more upfront testing of new features before we build automation on it. 

Event-based triggers not working is probably the biggest stability issue that we have run into, and integration services not working is probably the biggest gray area. Other than that, it is a stable platform.

UiPath is stable.

UiPath is a stable solution.

It is very stable. It is 100% stable. I am very confident of its stability.

I encountered some stability issues initially when I had limited knowledge. However, I now find it to be quite stable. UiPath stands out as one of the best options in our market when it comes to stability, thanks to its frequent updates and bug fixes.

Nowadays, all RPA vendors are trying to bring in something new every six months, but they don't get adequate time for doing the testing. As a result, there are multiple bugs. They should stabilize the release, do proper testing, and then only launch it. Otherwise, we need to wait for the next release for a bug to be fixed. Similarly, the training material for all established products from all the vendors is good, but with constant new releases, it is a challenge to get the latest material. They should release the training material before they start selling the product so that everybody is well aware of the features and the issues.

At the beginning of the project, there were some issues, but now, it is stable.

It is very stable. I am coming from Blue Prism where the software crashes from time to time.

UiPath is a stable solution. One of the reasons we left the Foxtrot solution was that it was unstable. If we had the same process running 10 times, we could get three different results. But with UiPath, we have never had any issues regarding stability.

UiPath is stable.

It is very stable. I would rate it a 10 out of 10 in terms of reliability. The tool is very secure. If a user wants to run it on a Mac, it works flawlessly.

It's very stable and provides accurate results for our organization.

This is a stable solution but stability is dependent on your configuration. If you configure your robots in such a way that every VDI that runs or every virtual machine that's able to run a bot has a backup, then it will be stable.

Its stability has been really good, especially lately. It has always been relatively stable, but as they've added things, it still seems to be pretty stable.

It is very stable. There are no questions about that.

As the platform grows, it's becoming a one-stop solution, but it also becomes difficult to integrate with your pre-existing IT solutions. It kind of lives in its own little bubble. Within that bubble, it has been self-sufficient and very reliable. We don't have issues with the bubble. It's a matter of integrating it with the rest of what we already use and are accustomed to.

I would rate the stability an eight out of ten. Sometimes, when the load is high or there are many users working at the same time, or when I'm working on different parts at the same time, it lags a little bit. There is a slight drop in performance.

Otherwise, it's very stable and secure software.

In terms of stability, I've not heard anything bad at my level. That means no bad news is good news.

The solution is very stable. 

It's been very stable. The only problem we had were some digital certificates and those aren't UiPath's fault. It's partly our fault and how we manage them. One of those got in the way and shut some stuff down. It's not really the UiPath platform. That really hasn't gone down on us at all. It was the certificates. 

On a scale from one to five where five is the best and one the worst, I would rate the stability of the UiPath platform at a four-out-of-five. The stability is a four instead of a five because the stability is not completely dependent on only UiPath. Underlying obligations play a part too. Sometimes when I am writing applications, I'm not up on how to handle every exception. That is not possible because a developer does not know all the scenarios an application can become involved with. In that scenario, the product can lag. But, otherwise, it is really a very good solution that is dependable and stable.

With respect to the stability, on a scale from one to five, I would rate this solution a four. We had some issues where we needed to get in contact with the support, and sometimes, UiPath crashes on our servers.

UiPath operates reliably around 80 percent of the time. However, automation speed can sometimes be hindered by internal applications.

To ensure the stability of our on-premises UiPath solution, a minimum of 1 TB of RAM is required for optimal performance.

Generally, UiPath is stable. We sometimes encounter servers that crash and we have to transfer the process onto another server but overall the solution is stable.

It is highly reliable, and we didn't have any issues with it.

The stability is good. We have run into some issues that they believe are more related to their environment than to the application itself.

The solution is stable unless we have a network problem or connectivity issues. 

The Orchestrator, cloud, and everything else have been stable.

UiPath is generally stable, although occasional issues may arise during upgrades.

UiPath is stable. Depending on a platform like this can be scary at times because it would greatly affect our business if it ever went down. That said, nothing bad has happened so far. It has been working well for us. We haven't had any issues, but it's important to be cautious. 

The tool is very stable. 

It's very stable.

UiPath is stable. 

We host on-prem, so I can't speak for the cloud support, though I've heard only good things. As far as stability is concerned, in terms of everything that we've moved into production, the only reason anything's ever broken, the only reason anything has ever not worked in general, has been due to agency oversight of people changing things without notifying the proper teams. As far as the UiPath's concerned, I would say it's pretty close to 100% stable.

They do monthly product updates and, after an update, the system doesn't lag or crash. It's pretty stable for the updates that they provide. 

Until now, I haven't faced any bug, software, or performance issue with UiPath. It has been a smooth ride and I hope it continues like that.

So far it has been very stable.

We really have not had a lot of hiccups or anything that's been difficult. The stability has been good. On a scale of one to 10, I would give it an eight right now and that's only because we haven't really tested the boundaries.

The platform is really stable. There's never been a point when it's been unstable or has had runtime issues. There have been really minute server crashes, unexpectedly. But I don't think that is due to the platform. It is more due to the server environment and the hosting environment not being configured properly. There are no problems whatsoever in terms of the stability as well as the performance of the product.

The stability has been great. I don't have any issues or comments there. I don't have any concerns with the stability of the company or the platform's software. We haven't experienced many bugs or anything like that. We're happy with the stability.

It is very stable. Once we got all the kinks worked out, there hasn't been any maintenance. 

We had a little problem with getting it to run at night. We moved it off of one platform and put it on another one, which fixed that problem. These are things that we encountered early on that went away as we figured out how to resolve them. Most of those changes that we made were internal to our process and caused by some slow responses within our Citrix environment. Once we resolve those, we have not had issues with the tool itself.

I have one person in IT doing deployment and maintenance. We also have a second person under contract if we need support.

With respect to the stability, on a scale from one to five, I would rate this solution four and a half to five. We haven't had any problems.

With respect to the stability, on a scale from one to five, I would rate this solution a four. There are a couple of things that break the robots, and it has to do with the technology itself. The user interface and other components are prone to error, and it's not one hundred percent automation. This is something that you take into consideration when you do RPA. They have also had a couple of updates over the past years where they made significant changes that basically broke the robots.

With respect to the stability, on a scale from one to five, I would rate this solution a four.

We've had some issues with stability, and I've talked to a lot of other companies who've had maybe more issues than us. It concerns ongoing support and the issues with bots not performing as expected or doing unexpected things as well. The problem is running into unexpected issues that can result from things that are not very readily apparent on the surface. This can be caused by underlying configuration differences in Windows, or patches that have happened, that sort of thing. It's still a challenge to manage and we often have bots that don't seem to have the issues when we are troubleshooting.

Sometimes it is our fault because we're not programming in enough breaks or logging enough to really track what's going on. It seems very dependent on the underlying operating system and things like update states of office applications. Occasionally, it'll just get stuck or hung up and we can't really figure out why, and that's frustrating. It definitely takes people time to go in and resolve those issues and figure it out.

It just seems like there's a lot of times where we just rerun the bot and then it works fine. I find it odd that it would stop at one point and then you just rerun it again and it works. A lot of those are, I will admit, due to input data issues or the system going down, or a website not being available or loading too slowly when it checks. However, I would like to see them continue to focus on stability as a platform, to avoid those as much as possible any issue.

UiPath is stable. All of my colleagues in other companies feel that this is highly stable compared to other tools.

The stability is an eight out of 10.

I haven't faced any stability difficulties, at least on the community version. 

The stability is good.

I didn't experience stability issues with UiPath in my current company, but I did in my previous company, where UiPath was down for some time. 

On a scale of one to ten, with ten being the highest in stability, I'm giving UiPath an eight.

Its stability is nice. We get regular updates throughout the year, and we have to install those updates, which is not a huge thing for us. We have not had any issues with that. I would rate it a nine out of ten in terms of stability.

UiPath has been stable in the past four or five months that I've been using it. 

I would rate the stability of UiPath as a perfect ten out of ten.

UiPath is stable, but it's crucial to understand new features when upgrades are released. Updates can cause problems because sometimes we don't know how to use the new features.

It is a stable product.

The stability has been good. I don't have any complaints generally about the stability. There aren't any particular issues I could name that would cause me to have a negative opinion, which I would say is probably about as good of praise as that perspective as you can get. 

UiPath is stable.

UiPath is a highly stable solution. We haven't encountered any bugs, downtime, or other issues since we started to use the solution. We also don't experience any instability when working with components in other projects. 

Its stability is good. In the last couple of years, I didn't have any problems. I would rate it a nine out of ten in terms of stability.

It is very stable. In most software, we find that when we increase the data size, there is some kind of decrease in network connectivity, a delay or lag. But UiPath is very stable because they release updates very frequently.

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of the platform as a four. It is a four because I haven't seen any outages yet but we may need more experience with the product to be sure it is totally stable when we are completely live.

There's no need to worry about the stability.

The only concern is as we move towards scaling it. What happens if the system goes off? Although it's not a big concern, we have been getting reassurance from UiPath that they have a solid backup of everything.

UiPath is stable.

I haven't had any issues with stability. 

UiPath is a stable product. 

I rate the stability of UiPath, eight out of ten.

It's stable.

I give the stability a 10 out of 10. It is very stable compared to other solutions.

It is extremely stable. We can actually trust the bots more than humans because it is completely error-free.

I'd say the solutions are around 80 to 85% stable. There are some areas that we have to reach out to support for, and they work to improve these areas for the newer versions. For that reason, I can't say the solution is 100% stable all the time. 

My impression of UiPath's stability is good. Compared to some other automation vendors that I've used, I would say that UiPath is more stable and better. 

With respect to the stability, on a scale from one to five, I would rate this solution a five. It's stable. The thing is, with the software, we have a few glitches here and there, but what I like is that we have the right support. When we actually reach out to verify, we get a faster response and also a faster solution. The responses are effective and fast.

I had an activity crash once when the permissions failed. When we were using that activity, it automatically created multiple activities. Even though we dragged it and used it only once, it created multiple activities. That only happened once.

It is stable. I would rate it a seven out of ten in terms of stability. 

I rate the stability of UiPath an eight out of ten.

Generally, it is stable, but it also depends on the usage. With any incorrect usage, it can crash.

It is stable. I would rate it an eight out of ten in terms of stability.

I would rate its stability capabilities eight out of ten.

UiPath is stable, but you need to adjust the process when a web application changes its interface. 

I rate UiPath's stability an eight out of ten. 

The solution is stable as long as you maintain it in a proper way. You need an admin and support team to take care of performance. 

The product has been stable.

UiPath's stability depends on how you implement it. If the solution is implemented correctly, it will work properly.

It's absolutely a stable product. It has been in the market for more than six years. Whatever solution we develop for a client is completely stable.

I would rate the stability a seven out of ten because we sometimes encounter errors.

UiPath is stable.

I give UiPath's stability a nine out of ten.

UiPath has good stability. They have monthly software updates, but they haven't caused any issues with our system. We didn't face any issues so far because everything runs smoothly. It's 99% stable.

The solution is very stable.

We haven't faced any issues with the stability of the solution because it is continuously evolving and upgrading. In some instances, we found that some solutions we had built in the past were failing, but that could be quickly fixed with their suggestions.

I rate UiPath eight out of ten. 

While UiPath has disconnected on a few rare occasions, it has generally been stable.

The solution is stable, depending on your infrastructure.

The solution is usually stable. Sometimes the activity doesn't work as expected. 

I'd rate the stability seven out of ten. 

I haven't had any issues with stability yet. 

Stability in UiPath is good, but this relates to the little bugs that my organization noticed in the community edition of the solution, not the enterprise version. Other than the minor bugs, stability-wise, UiPath is good.

The UiPath software is generally stable, but some of the packages within it can sometimes be unstable. For example, we have had to switch to older versions of some packages in order to get them to work properly.

UiPath is generally stable, but the stability goes down when we do Citrix automation.

So far, we haven't faced any downtime in terms of using UiPath. It has always been up. It also has a plan for exposing multiple endpoints so that if one goes down, we're able to use the other one. So, the stability has definitely been great, and we haven't seen any downtime until now.

It's very stable. Performance-wise and stability-wise, it's great. We're able to access it from anywhere. I have the Orchestrator app on my phone, so I can always keep track of the bots that we've developed and see how they're doing and everything.

The stability of the product is very good. 

If you look at the key components and the visuals, I mean the Studio, the Bot, and the Orchestrator, the Bot and the Studio are within our environment. We haven't experienced any issues. What is left is the Orchestrator, and we haven't seen any outages so far.

The stability does depend upon the applications we are using but overall the stability is good. 

It is mostly stable. We recently upgraded our UiPath Orchestrator, and we stopped receiving the emails that we used to receive in the morning about the status of our bots and jobs. I created a ticket, and they said that the particular version or update that I had wasn't stable. They provided me with a different version that was stable.

The stability has improved in the last two years. As they push more functionality on that and go more cloud-centric, I think it will be much more stable. We just got through an issue yesterday, but it was resolved quickly. We knew what to do. We could figure out the root cause. 

It is one of the very stable tools. We don't see any breakdowns happening within the tool. 

It is very stable. It can perform very well for small to medium complex processes. It takes a little bit of time to adjust for very complex processes, however. It takes some time to build and to develop and deploy for very complex processes. That said, it is very stable overall, with the caveat that, for very complex processes, it's difficult to build or manage.

Stability is something that we should consider in two parts. The first concerns the bots and how they are running the tasks on the machines. This comes down to what kind of developers we have because if you are developing properly, and implementing all of the exceptional cases that may occur during the execution of the process, it's very good. I haven't had any issues in cases like this.

The second part is the Orchestrator, and I haven't had issues with this either. In the more than three years that we have been using this environment, including the time in production and our test environments, we have never had an issue.

We have had two or three incidents because we didn't have enough space left on the database storage, but that was not related to UiPath. Rather, it is related to the infrastructure. Another time, the SSL certification expired so we had to renew it. Otherwise, stability-wise, we haven't had any problems.

In the past, stability has been great. However, more recently I have been facing some issues, and I'm hoping for some resolution. For example, we recently upgraded to the new orchestrator in Studio, and we had to upgrade a few packages also, In particular, the UiPath automation packages.

Some of our GUI activities, which are not fully backward compatible, have been facing some issues. Consequently, some of our bots have been impacted. We have already raised the issue and we are in discussion to find a resolution. This was the first time we actually faced an issue in terms of reliability with UiPath.

Our past experience has been very good, and I cannot say that we have any complaints regarding the reliability of UiPath solutions.

I rate UiPath seven out of ten for stability. The stability varies from machine to machine. If you have enough RAM and CPU, it should be fine. Sometimes it lags on computers with older processors. I'm using an i7 11th generation, and it works perfectly fine. Also, sometimes there are issues in new versions, but it runs smoothly in the latest stable version. 

I am absolutely satisfied with its stability.

The stability of the automation depends on how we establish the rules for a specific automation task. When we define a set of rules for rule-based automation, it tends to operate smoothly without lagging or getting stuck. The automation remains robust as long as the established rules are adhered to, even when there are changes in the user interface of the system.

I find it to be highly stable.

The solution's stability is quite commendable and even when we encounter incidents, we consistently update to the latest versions. We typically lag about seven months behind the latest releases because it takes around three to four months for the new versions to stabilize after their initial release. I would rate it nine out of ten.

The stability has been excellent, and we haven't encountered any problems.

It offers good stability capabilities.

UiPath is mostly stable, but we have encountered an issue after an update where a process created under a previous version may fail, so we need to update the bot. 

The stability is good, a 10 out of 10.

There is some lag. Otherwise, UiPath works well for us. 

It is pretty stable. We have not had major issues.

We've been using UiPath for almost four and a half years, and we've had one outage so far. The stability has been great.

The stability is good. I've never had a feed down and find it to be rather solid. 

The stability is good overall, and we haven't really had any issues. We do have certain processes, especially with certain systems, that are very finicky, and we have to go back and keep updating. I don't know how much of it is UiPath versus just the nature of automation.

Stability is one area where I'm really concerned. Sometimes it does behave erratically and I have to stop everything, and deploy it again, and it works fine. Therefore, I have some concerns about how it's going to scale out when there is a very high volume.

The stability is pretty good and the solution has not shut down. I have experienced a few crashes, but they are probably caused by my own computer.

The stability of UiPath is highly stable.

The product is as stable as it can be for the processes we use to expand on that. We do a lot of screen scraping and web scraping a lot. I want to move away from this in the future. However, the stability of those bots is going to ultimately be reliant on how that webpage looks.

We're looking at very specific parts of the website, such as the HTML tags. If those stay stable and we build our identifiers on those sites to be relatively dynamic, the process will be fine. 

It's a very stable product. I haven't had any issues. If I found or thought something was unstable or something, it usually ended up being me, or an operator error.

The stability is very good.

Stability is something that UiPath is working on. The new versions have added more stability and important features like test suites and the workflow analyzer. Adding features and improving stability is a continuous process.

The solution is stable because it has been developed precisely and it's already optimized. It depends on the user's input and on the architecture and the environments. We have very good stability.

This product is really stable, and this is true for the on-premises deployment as well as the cloud version.

The stability of this solution has improved since we started using it. Now that I have done an upgrade, it seems to be a lot better.

I was running High-Density on the 2016.2 or 2016.3 version, and I had a lot of problems. I couldn't determine whether they were just UiPath issues or it could be partly attributed to the client app. What we noticed was that if you log in as Console, you have far fewer issues than if you run High-Density.

These days, I would rate the stability a four out of five. 

With respect to the stability, on a scale from one to five, I would rate this solution a five. I mean we haven't used it too much so we haven't really pushed the boundaries, but for the stuff we've, done I would say it is stable.

UiPath is a stable solution.

UiPath is robust and always available. 

It is a stable product. In the last year, I have not found any kind of issue or server error. I did not have any issues where the server was down, so you can rely on UiPath.

UiPath is stable.

The uptime for our bots is almost 99.9 percent.

The product is stable. 

UiPath is a pretty stable solution. We have never had any stability issues with UiPath. It's in excellent condition as of now.

The solution is stable and reliable. 

UiPath is a stable solution.

It's a cloud-based solution. It's very stable, and we just need to make sure that it's up to date. Personally, I have not seen any bugs, errors, or performance issues with this. We are not using an on-premise model. It's cloud-based. So, the service is always available, and it's always quick. It's very stable, and I have no complaints.

The applications that we develop with UiPath are also very reliable. They don't crash or have any performance issues. They are very stable and reliable.

I haven't seen any degradation in terms of performance.

It's very stable, and we've never had an issue with it.

With the latest upgrade of Orchestrator, about a month ago, sometimes, when we are running our bots, the server crashes and the bot has to stop. There is a certain time limit to it. About two or three hours after it runs, it closes down and the bot stops and you have to rerun. There is some sort of a timeout issue.

It's something that we are still figuring out with the support team from UiPath. We don't know if it's something internal to our systems or if it has something to do with the upgrade. We have been in that loop for quite a while and have yet to receive a resolution.

The stability of UiPath is good. I haven't seen any abrupt occurrences in my time using it. Our production environment is always running. It's well-secured.

The solution's stability is 100% and really good because it never goes down.

The solution is stable. 

The stability is good. It is a fully matured software that is used by many organizations across the globe. Many big companies are using that. Timely updates are provided by them as well. We have no issues with that. They have taken care of the application version releases.

Stability-wise, we have had zero issues. It is working very well.

UiPath solutions are definitely very stable. It is very easy for us to build quality solutions and put them into production, then be able to trust the solution that we have put into production. For any automation center of excellence, that is quite important. You need to have a level of trust in your organization, inside of your environment and inside of your solutions. 

This also is attributed to the quality of our developers. We have strong, skilled developers. Without a product like UiPath, stability would not be such a great factor, especially if we had to go with a different approach or tool sets.

It's pretty stable. It's more of the architecture and how it runs because it has to leverage VDIs and as Microsoft releases an update, we have to be watching that process because it'll make the box really brittle. Any change to the UI anywhere will break and that's where we have to step in and fix it.

It has been reliable. We haven't had any reliability issues as such. Only the automation that we create could have inherent issues based on how a developer develops it. All of the out-of-the-box functionalities available in UiPath work as expected.

We always design a stable unattended solution that helps the business.

If fields are scattered, then the bot might get confused. 

Maintenance is handled by our support team. When something crashes, our dedicated support team monitors the bot. If the application crashes in production, the bot will send an application link to the support team and business stakeholders because the bot has faced some downtime in the application and kindly look into that issue.

Because I have automated a lot of enterprise solutions, I would go with the UiPath tool. They are frequently rolling out updates to the software. It is very stable compared to other tools in the market.

UiPath is pretty stable. Over time, I have seen them add new features and I have not found anything that wasn't working.

We have seen a few quirks here and there. Overall, we are satisfied with the stability.

We have only a couple of handfuls of automations running, which are very stable. So, we are not doing much maintenance at all. Maintenance needs half an FTE, if even that.

So far the stability has been good. With all of the low code platforms, it's actually more of a problem of what we've developed and deployed. It's how well we make our own software so that the platform will provide. It seems to stand up very, very well. I have not really had an issue. Anytime we have encountered a bug or whatnot, it's something we've introduced to ourselves, but thankfully there's a strong community where we can post questions and queries to get a response within a couple of hours.

This one area is lacking, but I attribute this to the constantly evolving platform. However, while there is some stability issues, they are quick to respond to them with updates. They are also very receptive to listening to feedback from the community, which is great.

UiPath is highly stable. 

It exhibits high stability. With a robust security department in place, we conduct thorough code reviews, contributing to a secure and stable process. On a scale from one to ten, I would rate it at nine.

The performance of the automation largely depends on the developers and the environment. For unattended automation, ongoing monitoring is necessary, especially when your team is actively making changes to the interface of the platform or system you're automating.

UiPath does sometimes go down, but compared to other automation tools I have used, it is more stable.

UiPath is stable. 

The stability of UiPath is very good. However, to build a bot requires us to go through many phases. Bot development is easy, however, getting access to applications can slow the process down.

The tool has 100% stability.

I rate UiPath nine out of 10 for stability. We haven't faced any challenges with UiPath's stability because it is a SaaS product. It runs on the UiPath cloud, and things are working fine. 

The stability of UiPath is a nine out of 10.

The stability could have been better. We started out with one developer license and then we had another developer license. When both developers are working in the cloud platform, it shuts down. I am not sure if it is solved yet.

The LTS version is very stable.

UiPath is stable. 

We're in the cloud and not on-premises, and I think the cloud runs pretty well. Up until last week, the stability was great. 

Last week, I had an issue with one of my licenses falling off of the unattended robot. I was surprised that it happened. I don't really know why it happened, and I'm working on getting it fixed.

The solution is pretty stable. That said, that'll be a question better suited for me in about three months after we've had our bots live. Since we're only in development and testing them in pretty controlled environments, it's harder to tell. It seems like it would be pretty stable. However, I can't answer that fully.

The latest versions are pretty stable. I haven't seen any issues with stability.

My impressions of the stability are largely positive. However, I'd like to see more emphasis placed on error handling for production.

We've had only one outage, and that might've been our internal issue. Otherwise, it has been rock solid.

So far, we have had very few issues and the issues really have been around very complex knowledge. We have reached out to UiPath to get advice, and they responded, and it hasn't been bad at all.

I'm satisfied with the stability of UiPath. It's good.

With respect to the stability, on a scale from one to five, I would rate this solution a five.

We don't see many failures, and this is partly because of our approach. We start by creating something called a heat map, which I learned in some of the training from UiPath. The training clearly explains how to handle errors. It includes which process to automate fully and which processes should be automated partially, with a human in the loop.

We start with the right approach. We understand the process and we have the heat mapping that gives us full clarity of where the exception flows are and how to handle them. So when you do that, it becomes second nature to handle those exceptions. We are pretty comfortable, and we are applying the best practices, which adds to the stability. 

The stability is quite good. You have other options, such as Automation Anywhere and Blue Prism. UiPath will be like coming out with new revisions in the coming years that will continue to compete with those.

Even now, it's quite stable and quite reliable, even if the changes which are coming, in the much of the deployment, are felt good. There are frequent revisions. I have no experience in other automation, however, from what I've seen, even as it changes, it's stable.

I have had issues with previous versions but the latest updates have resolved my problems. As of now, the stability is very good.

With respect to the stability, on a scale from one to five, I would rate this solution a four. In terms of attended automation, we did have a lot of issues. We have requested lots of product enhancements, which then came through the pipeline. Initially, we did see a lot of issues and they had to make some changes to cater to our needs. Also, we have some more requests that have been put in the pipeline to make it a bit easier for us.

On a scale from one to five, where one is not stable and five is very stable, I would rate the stability of the UiPath platform as a four-and-a-half. I've only seen one or two buggy behaviors, so I think that qualifies as extremely stable.

On a scale from one to five, where one is the least stable and five is the most stable, I would rate the stability of UiPath as a five. It is very stable. We have never had any issues with regards to UiPath. The actual problems seem to be network issues and our environment.

I would rate the stability as a five out of five. it hasn't gone down yet.

It's stable. We haven't really had technical issues.

The solution is stable. From what I have heard from my team, it's almost always stable. 

I rate UiPath's stability a nine out of ten. 

UiPath is much easier to use. Stability-wise, the solution has a lot of scope because there are many complex things in other tools. UiPath is a stable solution.

UiPath is a stable solution.

It's very stable. I haven't faced a problem with UiPath Studio. I would give it a 10 out of 10 for stability.

UiPath is stable.

UiPath is stable. 

In the past three years, UiPath has been highly stable even though the environment has changed frequently.

We find the solution to be stable. It's not just building the robot - it's being able to sustain it. So far, we trust its capabilities and have not questioned its stability.

The stability is great. What they've done is pretty impressive. They're going to be here for the long haul.

We found it to be very, very stable. We have not had any issues since we went live, so that's also been very impressive for us that it's extremely stable.

This solution is very stable. Any complaints I have come back down to package management and custom issues with custom libraries. Outside of that, upgrades are really quick and really easy. We have bots disconnect so frequently that it is easy for us to catch issues manually.

UiPath has always been up so stability is not a problem.

It's stable. It has 99 percent uptime. 

Sometimes, when we are dealing with a large set of data, it becomes slower. I don't know if it is something to do with UiPath or something else, like the operating system or the connections. It is almost always stable, but when dealing with large data, it becomes a little buggy and slower. Sometimes it freezes and I have to turn everything off and restart it.

I'm not worried about the stability of the product. If others are using it in the cloud with much more complicated processes than we are automating, it's not really a concern of mine.

It's pretty stable. We haven't run into any issues with operating totally different packages. There have been some things where I wish there were more restrictions in access groups that could be applied within Orchestrator, but other than that, it's pretty good.

The solution is stable. I don't see any problems.

The solution is stable. 

It's stable now. 

UiPath has a number of offerings: on-prem Orchestrator, Automation Cloud, Automation Hub, Cloud Orchestrator, Task Mining, Task Capture, etc. Sometimes, it feels like other new areas are getting more focus compared to areas, like dashboard Insights, which should be more relevant. They should focus on these other areas to make the cloud offering more robust. Though, they are working towards it and releasing updates. Therefore, eventually, they will look into it, work on it, and iron out any kind of discrepancy.

I would rate their stability as three to four out of five, but I would say that's probably because we don't know how to use it best. That is why we sometimes have issues that something's not working.

With respect to the stability, on a scale from one to five, I would rate this solution a five. I have never had any problems with the platform itself. I haven't had to restart the servers or anything like that.

I'd rate the stability five out of five.

The stability is not that good yet for whatever reasons. We have a lot of safety critical things that have to be 99.999% availability, so we're struggling a little bit with those. For the non-critical processes, it does a great job.

I would rate the stability of Uipath eight out of ten.

I would give the stability of UiPath a six out of ten. I've experienced some issues with it in the past.

The product is very stable. When we deploy it in the cloud, there is no need for maintenance. UiPath manages everything. Maintenance of the configuration has to be done by us.

The solution is stable. 

UiPath is the most stable platform.

We had some issues with stability because of some unattended robots. During execution, there were stability issues.

The solution is pretty stable. You may have version issues because there are a lot of updates, but that is not a stability issue. It is always important to make sure you have the latest updates. 

The solution has been very stable across hundreds of automations. 

Its stability has been great. I've never seen it break or crash. It has been very reliable.

It is capable of doing various tasks at the same time.

We have not experienced any downtime or issues.

Starting from version 20, UiPath has been very stable. Prior to this, it has not been 100% stable. That said, we have not had any troubles with the platform in general.

The problems that we have encountered were when we tried to upgrade or to migrate by uninstalling and reinstalling the Orchestrator. There were some internal issues where people didn't read the communications that we put out.

Generally speaking, Orchestrator is very well built. We have put a lot of stress on the system and haven't experienced any problems with performance.

My impression of the stability is that it's like any other software. We have never had a problem with UiPath and the platform has been stable enough to enable us to scale a lot. 

We haven't seen any issues with stability. It's definitely been good.

I am not worried about the stability. I may be naive, but if others are using it in the cloud with much more complicated processes than what we are automating, it is not really a concern.

The stability is amazing. Years have gone by and obviously, the product has changed a lot, however, of late, the last couple of years have been great stability-wise.

UiPath Robots are quite robust, and from a maintenance perspective it has become easy, if you create logs. It's pretty good.

Robots on the SAP system seem stable, but on the web they sometimes lack stability. Still, it's not a very common occurrence and I have overcome any issues with the help of the Trilogic. For example, we had an issue while getting an email from Outlook. A UiPath robot is not able to do that. It will time out. With the help of the Trilogic, we were able to overcome that.

Initially you have to put some effort in to obtain stability and then it is mostly stable. Some maintenance is required, but that's most probably when requirements change, or to add to the stability, but it's not a lot overhead right now for us.

Four to six months ago, this was not the most stable solution. We had a lot of issues, especially during the summer and early autumn. The system would fail, or would not be accessible, or we had lost some of our logs.

Right now, the tool is working and is much more stable. It shows that they have put an effort into making it more robust.

I would rate their stability as four out of five.

In cases of high scalability when we have one process and many of us use that process, we sometimes have problems. When one process uses about 24 robots for 24 hours, we have problems with it. I think when many robots work at the same time, something goes wrong in orchestrating tasks between robots.

With respect to the stability, on a scale from one to five, I would rate this solution a five. It is quite stable.

On a scale of one to five, I would rate the stability of this solution a five.

I haven't found any problems specifically using the tool. I have only had a few errors, but that is because of personal mess ups when I'm creating processes and a field is messed up or a variable is incorrect. I haven't had any crashes or faults with the free Community Edition and the bot that it has come with.

At times, when I restart the system, the deployed robots take time to connect to the UiPath Orchestrator. Overall, I would rate UiPath a nine out of ten in terms of stability.

I would rate it an eight out of ten in terms of stability.

UiPath is not as stable as I would like, and I hope to see improved stability going forward.

UiPath is extremely stable and that is why customers ask for the solution.

UiPath is stable.

UiPath is stable.

UiPath is a stable app; I give it nine out of ten for stability.

The solution is fairly stable. We have to perform maintenance on things we are doing and see some infrastructure issues for on-premises users. Many of these issues would be addressed if we switched to the cloud so that is under consideration.

The solution has been 95% stable. 

We experienced some performance issues because our libraries are growing and we experience crashes from time to time. This usually means we need to reboot. The stability could be improved in this regard. The ability to handle large-scale applications or multiple applications could be improved as our operations and libraries are going to continue to grow. Currently, our libraries need to be split and this creates more maintenance for us. 

It is stable.

UiPath is a stable solution.

The solution is stable, it's a reliable software. 

In terms of stability, the robots have been running well. That said, we've had a few failures that we had to go in and fix, however, it was a pretty minimal effort to fix them. I'm not sure of the exact reasons. I remember my developers were telling us one failed and we needed to go figure it out.

It wasn't like an all-day fix. It was just a pretty quick fix which required simply stopping it and restarting it and then it worked. 

In general, for stability, it's been so far so good.

I don't have any problems or concerns about the stability right now. The biggest concern I did have at the time was the fact that we've already invested six people in this in terms of the robotic piece and we're going to have a lot more. Since we've re-allocated these resources, and I have potentially 100 people where I could also reallocate resources, I worry about if something does happen or it doesn't work or there's no backup. If something goes wrong, I don't have employees to backfill as they won't exist. That's my concern. That hasn't happened yet, and I hope it doesn't.

The solution is very stable. I have not faced any difficulties at all. 

While the stability is fine, with a license that needs to be paid yearly, UiPath will put out a new version annually. That way, when companies go to renew, they often need to upgrade or pay for a new license. The product does this to keep earning money year after year. 

Stability-wise, UiPath can handle the different varieties of stability on the applications you are automating. 

For example, if you choose to automate applications that are expected to change in the next few months, then UiPath cannot help you. That takes an entirely different form of planning. However, the more stable the process, the less likely any part of the process will change, the better UiPath can assist. 

I would rate its stability as five out of five. With any tool, there have been occasions when a job did not trigger or aborted, but that's been very rare in my experience.

With respect to the stability, on a scale from one to five, I would rate this solution a four. The tool itself is quite stable and I haven't had any real issues with it. The issues that I have had tend to be with Citrix or the environment that the robots are running in, and not the platform itself.

The stability is fine. The only factor we have is a finicky customer. We need to help them with their choices, changes, reversals, augmentations, but it seems to be pretty simple and intuitive so far.

I think it's stable. I haven't had a chance to build a bot that runs 24/7. For the bots that I have built, it takes under two minutes for the process to run and it runs every hour. At the end of the day, if I look at the logs, I don't see any issues. If a bot fails for whatever reason, it's most likely due to a process that changed.

From a bot-development standpoint, we use all kind of best practices so that the bot will not crash. At least, if the execution stops or terminates, it will be graceful, versus a rash termination.

It's fairly stable.

The product is definitely reliable. It gets the job done. The difference is in how you design it. When you start as a developer, you tend to always take the longest route as part of the learning process. Once you get used to the product, you realize something can be done in two steps instead of five.

A lot of people rely on what I design, so if it doesn't work, I immediately get a call that 50 people are waiting for something. This happens, but rarely, as it works perfectly.

It can be complicated to get a stable solution, but once you're over that learning curve, it's very easy. At first, it's complicated to figure out how to get a stable solution using UiPath.

It is stable. Our organization has licenses because we cannot upgrade the application in sync with the Community version. The enterprise has to stick to one version for a certain period or whatever tenure has been mentioned in the license. The Community version is the playground for UiPath. They upgrade it, and all the beta version updates are there. They come to know how things are going and what are the responses and challenges.

Excellent stability.

UiPath is stable.

I would rate the stability of Uipath eight out of ten. We have had some stability issues with our VMware.

It's very stable.

I'd rate it a seven out of ten in terms of stability.

The solution is highly stable; I rate it 10 out of 10 for stability.

I haven't faced any issues so far. It has been smooth. I would rate it a 10 out of 10 in terms of stability.

We've never had an issue with performance stability.

We have been using this for about one and a half years, and it's highly stable so far. 

With respect to stability, the general system is stable. This includes the robots, Automation Cloud, and the Action Center. However, we have had a lot of downtime with UiPath Apps. It had been one or two days per month when our processes were getting blocked and although many of these issues are resolved, last month we had recurring issues with downtime.

The issue that I mentioned earlier, that sometimes it wasn't able to find the elements, was the only issue I saw with respect to UiPath. Otherwise, nothing was breaking and nothing was problematic on the UiPath side.

The stability of UiPath is quite good. In some particular areas, the bot struggles a bit and we have to implement Human in the Loop. Those cases are where the bot can't do certain validations. But overall, the solution is stable and accurate in the results.

I haven't seen any issues with UiPath's stability. 

Sometimes clients think that they can just do something and then it runs forever. People who actually work with it know that it's going to break and you're going to have to fix it. However, that's part of the process. When it first starts running, you're going to have to make it better. There needs to be managing of expectations. It's going to give you value, however, it's not going to be perfect the first time, which is just not even the automation's fault. It's sometimes the systems. You have to learn the quirks of the systems and the systems that it works with. For example, a website might have a pop-up that you wouldn't expect. It'll break, and clients will ask "why is this broken?" You have to explain the bot doesn't know how to handle everything.

The stability has been very good. We've had no issues with stability at all.

Stability-wise UiPath is good, however, it releases twice yearly. Therefore it will be a little hard for people to upgrade in-house each and every time. Clients also question why it's necessary every six months to upgrade. It won't be reasonable for the management. Every time when an upgrade is available, we have to complete the regulation for the previous use cases and whatever we already have deployed at production. 

When redeploying, everything is kind of a hectic task. Once in a year is okay, however, multiple releases in a year is a bit much. Clients would not be aware that yearly this many releases are happening and every release will have something more to add, that there are changes. Having to adapt to changes is something that is very difficult to make the client understand.

Until now, I have seen good uptime. There were no disruptions in data. I've seen the services running properly 99% of the time. Their logging mechanism, job schedules are also running properly in Orchestrator. So, it is a stable environment.

The robots could be a lot more stable, which is another area for improvement. The stability issue with UiPath is a prominent one, especially in comparison to other tools like Blue Prism. I feel that there are a lot of errors that are caused by the UiPath framework, as opposed to the robot design. Sometimes it's just very unreliable and crashes unexpectedly, which creates serious issues in terms of reliability. In early deployment, it always happens that it's very late nights, and there's a lot of babysitting processes. The robots need it because you never know what's going to crash.

In comparison with other RPA tools, it is average when it comes to reliability. I would rate other tools a little bit easier to manage expectations as to what you can reasonably expect to go wrong, and what you can reasonably expect to break. With UiPath, our developers, even our experienced ones, oftentimes get errors that we've never seen in our lifetime. This is partly due to the flexibility of UiPath, with it being so easy to adapt to all types of applications and all types of environments and it being so malleable. It is one of the most versatile tools; it's industry agnostic, platform-agnostic, and tool-agnostic, but that flexibility creates a lot more room for error in the code. It means that a lot more things can break or interfere with each other, compared to other platforms that are perhaps more niche and more targeted in what they're actually trying to solve.

It's phenomenal. The stability is really good but some of the releases have been a little shaky.

The tool is very stable. The product's stability depends on the processes you configure it with. 

The stability is good. I am satisfied with it.

It's stable.

The solution is very, very stable with no issues when we deploy bots. 

UiPath is stable. Like any product in the early days, they were updating all of the time. That used to not sit well with our bigger customers because of their update plans. As the product has matured, it's become more stable and the release plan has become structured. You now get four updates a year. It has become more mature.

In terms of stability, that's where there's room for improvement.

It just comes down to a lot of selectors and items of that nature. Selectors can fail randomly and then start working again and can cause issues. That's been our issue with stability.

I haven't had any problems or concerns right now concerning stability. The biggest concern I do have is that we've already invested six people in this. We're going to have a lot more that will, more or less, not have the robotic piece as part of their job. That work will be reallocated. I have about a hundred employees that UiPath could technically reallocate.

When I look at that, I worry about if something does happen or it doesn't work or there's no backup. Then, suddenly, I don't have employees. Right now, we can jump in and some humans can do the work if necessary. My concern is that in the future they won't exist. This hasn't happened yet. I hope it doesn't.

Other than the issues related to the exception handling and UiPath getting stuck, it is very stable.

From what I have seen, the biggest factor for availability is the strength of the internet connection. Whether the deployment is on-premises or cloud-based, they both are the same in terms of stability. I have not seen any deviation between deployment types.

The stability is good. Everything works well and I don't have any production bugs. I only have positive feedback, It works and there are no unexpected errors.

So far we have not had any issues with the stability.

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of the UiPath platform as three right now. There are some nuances in it that are throwing some error codes when reading the QR codes. But we are in the process of working with UiPath to get that issue corrected.

This product is very stable, but we have some issues with security.

On a scale from one to five with one being the least stable and five being the most, I would rate the stability of UiPath as pretty stable. For us, it has really been a five.

With respect to the stability, on a scale from one to five, I would rate this solution between three and four. Sometimes there are issues where something is not working, although there are probably times where it happens because we don't know how to use the solution in the best way.

On a scale from one to five, five being the most stable, I would rate the stability of the UiPath platform as a three. We've had a lot of issues with bot stability. I don't know if it is how we go about development or if it is the platform itself, but we spend too much time trying to fix all the bots that seem to be breaking.

On a scale from one to five where five means the product is very stable, I would rate the stability of the UiPath platform a five. It works and nothing breaks that is directly related to the product itself.

With respect to the stability, on a scale of one to five, I would rate this solution a five. We haven't ever had any issues with it.

We have had stability challenges. However, I don't know whether it is product-related programming-related, or if it is our core systems which are failing. So, we have instabilities, and whether or not it is UiPath, that I don't know.

The stability is good, I've never encountered any major problems. UiPath works with websites and systems which are famously unstable, but it gives you the tools that are necessary to deal with hiccups and if something is not stable. So, if you add proper error handling to your robots, it works.

UiPath's stability is quite good. We don't see any problems with the stability of the platform application. All our problems stem from the basic systems that we operate on, which are quite vulnerable to network problems, time outs in various systems, etc. However, these have nothing to do with UiPath. Perhaps some of the things which are on the road map will help with the debugging of some of these issues.

One of the things that we are lacking right now is not stability, but usability with debugging, e.g., when you can't see what went wrong. We have to look through 50,000 pages of logs or so. 

Recently, there was a software update of StudioX. We had some bugs. I would rate it a five out of ten in terms of stability.

It is relatively stable, I would rate it seven out of ten, as it should be improved.

It is a stable solution; everything seems to be running pretty smoothly altogether. The biggest issues are not on the UiPath end, but on our company's end like, network issues and issues like that keep popping up every now and then.

The stability is okay and chances of bottlenecking are not much. Occasionally there are some errors and the robots do crash but overall that is not an issue. 

UiPath is stable, and each version comes with new advantages. UiPath supports .NET versions, Windows Legacy, and current versions of Windows.

UiPath is an unmatched platform for robotic automation services. One of the most stable and up-to-date databases to automate and reduce workloads for organizations.

UiPath is a stable solution.

This is a stable solution and we have not experienced any crashes. The challenge we have experienced is when developers do not document requirements correctly but we have had no issues with the software itself. 

We actually had to spend about four months of maintenance to make sure that we got the solution to how we wanted it. We brought in a contracting firm and they didn't know the company and they just kind of said, "here's what bots can do." 

What we did is we did an assessment program for two months. During those two months, we looked at what they built, which was great. This got us up and running and showed us what's possible. 

Then, we took those two months to identify, for example, if the database maybe should have been set up a little better to interact with our other databases. Or if the coding should have had different paths of risk that they didn't know about. If you don't know the business, you don't know the risks, and therefore, you don't know how to set it up. That's why we did all of that assessment and then we spent four months fixing it to adjust to what we thought was a better path or a more stable path in order to support the robots.

Stability has been quite good. I see technical glitches once in a while in the Studio, but when you're running on Windows, it happens. The glitches don't happen very often.

We use UiPath AI Center, UiPath AI Computer Vision functionalities, and Document Understanding. These AI features came into the picture from 2019 onwards. First, we received updates using UiPath Computer Vision functionalities. Then, we received AI Center, which was not stable in its initial days. However, during the first quarter of 2020, we received version 2, which seems to be more stable. From there, we received general availability versions with integrations on UiPath Studio and UiPath StudioX. These work much better, as compared to the initial versions. So far, all the components of UiPath Computer Vision, Document Understanding, and UiPath AI Center work well. 

After deploying the bots in production, processes are very stable, unless something happens with the machine. You don't have to monitor a process every time. So, I am very impressed and satisfied with things.

We are looking to update to version 20.

In general, at least for us, product has been very stable, but we are not doing extremes with it.

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of UiPath platform as about a four. There are two activities that we use that fail about 5% of the time. UiPath is fixing that — as far as we understand — and so we should get a solution very soon.

So far, we have not noticed any crashes or any issues with the platform itself.

I'd rate the stability four out of five. We haven't presented problems but sometimes with the UiPath robot, the robot attended license breaks.

The product, itself, is generally very stable. On a scale from one to five, I would rate the stability a four. We do have situations where we've run some updates and then ended up with some OCR things breaking on us. But overall, we build automations for our customers and they don't really know that there are any problems whatsoever, because they're generally pretty easy to resolve.

If I'm using it as an attended bot, it's pretty stable. When you discussing unattended bots, anything could go wrong in the entire stack. We have found times, if I run UiPath for a week, and it needs to simply loop a PowerPoint presentation, come back in a week, then sometimes the PowerPoint will be dead. It is harder to understand if it was UiPath's fault or if it was because the device decided to do a random Windows update and restart itself. It could be a litany reasons, but even then, I can't be 100% confident that the unattended bot is going to run forever.

I was recently reading about the document processing framework that they just implemented. I gave a demo two weeks ago on the Computer Vision functionality that was in beta. So the sustainability is there. They're focused not on just how good RPA is and on making it better, but they're also integrating it with future-tech. That is where the stability comes in.

Stability depends on the type of structure that you are putting in place. I think it is important that you run 16GB, with not more than three or four processors in parallel.

Most of the time, the product boils down to making something that works by itself. 

I haven't encountered any real issues with the stability of the product. It is hard to evaluate since it works through so many systems.

The product is stable. 

The tool is stable. 

The solution is stable. 

The stability is good, but they keep upgrading versions. If you want some of the new additions, sometimes you have to take a beta version.

UiPath is stable. The automations we have in place right now are stable. 

I don't like the stability very much as it has minor bugs.

You see that processes break without any reason. When you check the system, check every log, even view robot logs or logs in the network level and you see that it has, it's only then that you realize the issue was a bug from the UiPath platform. Once that happens, you must go to the community and explain the situation to each other. The good thing is, there is a community right there and you can learn from each other. 

The solution is very stable. 

We only use the stable versions, regardless of whatever they are releasing, to avoid bugs and errors. In the stable versions, we have never found any issues or any bugs. If there is any issue, we have a team that will contact the UiPath team and we will get quick solutions. But so far, we have never had any problem or issues with a stable version of UiPath.

UiPath is a very stable solution.

With respect to the stability, on a scale from one to five, I would rate this solution a three.

The stability of this solution really depends on the developer or the execution. It's not always a UiPath issue. If the process is unstable, it's the issue of the business case and not the actual execution of any development. So it really depends on how you use the platform and how you understand it. We will use a more stable technology, such as alerting through an API, before we go to the UI path.

Now that I've done an upgrade, it seems to be a lot better. Because I was running high density on the 2016.2 or 2016.3. I had a lot of problems, but I couldn't work out whether or not it was just UiPath or our client app that was timing out. But, we noticed that if you login as console, you have far less issues than if you run high density.

These days, the stability is a four out of five. Back in the day, it wasn't.

I would rate stability as a five (out of five). We have not actually had any issues with UiPath. Most of our issues have been with just platforms changing, breaking, and the regular maintenance.

When the complexity increases, the bug related issues go up. There are limitations to utilizing RPA software, in general, where sometimes you have business leaders who think something is a good process. Then, they ignore the technical advice to not move forward, or choose to. Thus, you're left in a situation where you're trying to automate a process that isn't great for automation.

The stability has been good, so far. I haven't had any complaints.

Completely stable and reliable with all the scheduled jobs. It gets the job done in most of the cases.

We are proud to say that we have not encountered any issues. Yes, sometimes I hear some colleagues like, "Oh, I have KYC and he stopped." Well, there are also some reasons because, if your password expired and, guess what, somebody needs to update it before it's expiring, the robot will stop. Yes, but so is if you're a human and your password expired, you need to change it.

Compared to other tools, UiPath is very stable, as well as easy to install, manage, and upgrade.

UiPath is quite stable. I haven't seen any downtime. I can also pause the upgrade itself if I don't want the upgrades to cause instability. The long-term version is available as well.

No robotic solution can ever be classed as stable unless there are no change dependencies. It will always require more support than any other core technology - its the nature of the beast.

Stability-wise, it's really good. When it comes to backend automation, it's amazing. With the UI automation in mind, I would say it's quite stable. However, there is a chance of errors. I would say, if you're doing a process based on a UI interaction, the stability it gives is somewhere around 5% to 10% on each process. Again, it depends on a number of things, such as the start-up package you are working with and/or what is the response of that individual. It's something that somewhat falls outside of UiPath, in terms of stability, however, when it comes to the process, everything counts. Even, for example, electricity counts. If there's system slowness or a system crash, it can affect everything, even if it's not necessarily caused by UiPath.

If the application is working fine, without making any updates or changes, then the bot will work as expected about 95% of the time. However, if there are any changes to the end-application made by the developers, or there is a content change, then we definitely have to align to those changes and it will take time.

Generally speaking, we move a process to production once it is stable.

The stability is usually really great. However, at this point, we are uploading a new version because the stability is not right. They told us that our version, 18.4.5, is not 100 percent compatible with Orchestrator. Therefore, we don't have the stability that we had before.

With respect to the stability, on a scale from one to five, I would rate this solution between three and four. For exception handling, it means that a senior RPA developer has to understand the reasons behind the process. If they have not been exposed to it then it is easier to perform some simple fixes and continue the process.

Ease of use has definitely exceeded expectations. Initially coming in, UiPath had some features that needed to be implemented that weren't quite there yet. Now, we are on 2018.4 and all of the features that we desperately needed are there. Thus, ease of use has been pretty great.

The stability needs to be improved. The UiPath selector is consistently failing.

I rate UiPath nine out of 10 for stability. 

The solution has been very stable. I'd rate stability nine out of ten. 

The solution is stable. 

It's stable. I would rate it a nine out of ten in terms of stability.

Being cloud software, it's stable. They just need to make sure that it's up to date.

This is a stable solution. 

Both on-prem and cloud solutions are very stable. The cloud is stable thanks to the UiPath team and on-prem, in our case, is stable thanks to our customer IT infrastructure team. Between the product itself and the infrastructure, be it Azure Cloud or on-site infrastructure, the stability is good. If there's any instability, it could be related to the people involved in using it as I've had a good experience with both cloud and on-premises stability.

There are occasional errors happening, which cause the software to freeze up. However, this is not more than once every two weeks and I'm always able to recover the project. I would say it's stable. Regarding working automation, I also have no problems as the errors that we have on ready robots never result from UiPath's issues. They result more often from infrastructure issues or robot problems.

The robots are pretty stable. It just depends on the way they are coded and how robust the developer has made the solution. If they have taken care of all the edge cases and of the possible areas of failure, the robots are predictable.

UiPath itself is very stable because it interacts with so many different applications. I noticed in the past, at times, when using it with browsers, for example, using it with Google Chrome or Firefox, occasionally Chrome or Firefox will update and UiPath can take sometimes a week or two to update with it. For that week, you're able to use any solution that involves Google Chrome or Firefox, because it's waiting for that update. I've seen that happen with a couple of different applications, not as much recently. UiPath itself is very stable because it can interact with anything. If anything is updated and UiPath doesn't have time to update drivers to match that, sometimes you can get left a little bit stuck.

We found it to be quite stable.

The stability is as good as the developer makes it.

It is a stable solution. However, if your applications are changing, you will have to do some manipulations in the code. Now they have a feature where you can keep your UI things in your config or in the assets, which is helpful. It is easy.

UiPath is very stable.

The solution is stable and we have no problems running bots. 

It's pretty stable. I have never gotten errors on the connection between the bots, Orchestrator, and Studio. 

The errors I have found are generally related to the network or to a virtual machine with fewer resources than the minimum requirements. 

The overall execution of the automations is pretty fast, even when dealing with high volumes of data from Excel files, compared to VBA or another scripting tool.

The stability of the solution is excellent.

I haven't had much issue with stability.

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of UiPath platform as a three. We had a lot of trouble initially, most of which was our own fault. Migrating all development, testing, and production, to identical virtual machines to ensure parity helped tremendously with stability and reliability. We still have to be very careful with selectors though and have learned to not trust the default capture particularly with Java-based applications.

With respect to the stability from a bot perspective, on a scale from one to five, I would rate this solution a four. It has been pretty stable for us.

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of UiPath platform as a three. Right now, we are having some connectivity issues, between Orchestrator and our environment. We have been working with our infrastructure support team and UiPath infrastructure report team to figure out what's going on. We are working through the issues and I'm very impressed with the support that we have been given, but we have got to figure out what the issues are and solve them.

We have not experienced a whole lot of issues with UiPath at all internally. 

In some of the pilots that we are developing for our partners or for our customers, we haven't seen any major big issues or bugs.

The stability of the solution is mostly good. Sometimes there are bugs.

We've created a bot within our collections team. We are doing a reconciliation, and since implementing the bot, which was at the beginning of this year, we hadn't needed any changes onto the bot. 

We've been involved in automation for ten years or so, and UiPath for about two or three. We've had no major issues from a stability perspective.

The stability is excellent.

The solution is very stable compared to other enterprise tools. Even if there is an error, if you handle it properly, everything works perfectly. From the point of view of UiPath developers, everything is done on a very high level.

For the most part, the solution is stable. We did encounter one problem when we were testing. Apart from that, we did not encounter any issues. 

I can say it's a very good tool from the RP perspective. It is helping us to get our work faster, saving time as well as offering multiple functionalities. We haven't had any issues with it. 

Everything is good - except the capture part. They could improve on that as we are getting less accuracy as compared to the other functionality. Other than that, the rest of the components are fine.

I did come across an issue very recently where, when I had to update the version of the Activity package I used for a particular deployment, the Data Table Activity, it did not list the way it had been listed. I raised a question in the forum, but there was no clear answer. Apart from that, I haven't seen any other instability with UiPath.

There are times when you need to shut down the automation and restart it. Other than that, it is very stable.

It is too early. We are still in development.

Stability is a part where I would definitely rate UiPath a five out of five. It is really the best among all RPA products in this regard. 

There are not many complaints on the stability of this solution. Though the regular updates of the Community Edition have given me trouble at times, it has been quickly resolved in the subsequent updates. I think that the UiPath Forum portal is one reason for this.

UiPath is pretty stable and if you have any issues with a new version you can rollback.

The solution is fairly stable. I would rate it as four of five for stability.

The solution is fairly stable. 

I would rate stability as a four (out of five). I had some cases where Orchestrator didn't work in it. We couldn't login and the platform was slow.

With respect to the stability, on a scale from one to five, I would rate this solution a four. There are some issues we've run into where we just can't exactly figure out what is causing the problems.

A robot would run through a process two to three dozen times with no issues and then on the very next run, it will stall in the middle of the process. When we tried to debug it, we can actually replicate that stall but clearly, it's not throwing an error. There's no rhyme or reason to why. It just stops and it just kind of hangs. I would say that it may be a stability issue.

Stability looks good except that we see that when we run the bot sometimes somewhere in the middle it fails. It will recovers, but I don't know why and can't answer to my customers why. I don't know if something can be done to eliminate the failing piece. I don't know whether it is a stability issue, but it should be handled in future. Other than that, stability looks great.

The stability is pretty good.

Our Citrix environment works, but it is quite unstable. It takes a lot of processing time because it is unstable. We have to do a lot of checks and so on.

The system is quite stable. However, we need more experience in coding it to make it even more stable.

The product has been stable, so far. It is rare that it goes down.

Its stability is very good. 

The stability of the solution is really improving itself from where the organization really started to embark on automation. Year over year, they've added new features, and really what made automation more of an omnichannel approach.

It's not just another tool to develop bots, but it's a tool that has process mining and tax task capturing. It's something that only comes in with an end-to-end approach, rather than other RPA tools in the market that only have point solutions just for development and really don't have an end-to-end solution.

The stability is very good.