The security aspect of Kryon RPA is good, which is why several banking and financial institutions are using it. As for stability, it ultimately depends on meeting the expectations of the individual customers.

Based on how we use it, it has no breakdowns. It's very stable. I mean, it's been months since we encountered any breakdowns.

The stability is pretty good. The only unstable part is Studio where you build this stuff. In our version, the 5.25. It has a memory leak. If you leave it open for too long, eventually it just freezes. Saving your work, closing, and opening it just once a day is all it takes. However, this is a bug that I have noticed about the stability of the actual tool. Our production console and robots have been rock solid.

We are still a fledgling operation with it. We have one guy who works part-time on the PDF and another full-time contractor working with the business to build more bots and wizards and also finding more opportunities. Then, there are two of us who are dabbling in it in addition to our regular jobs. 

It is also helpful for certain one-off updates. I am a support analyst myself for a lot of our software. People in the business will come to me with really simple problems. E.g., HR had to send out an email to every intern with some of their employment credentials and links to sites for things that they needed. However, they all had to be personalized. Each email needed to have unique information to each candidate in it. So, they built the template real quick. They handed me the email and we dumped a list of the interns from our HRS system on it. We just threw that in the bot real quick with a couple of loops using the email template with some variables and were able to send out an email to all the interns in minutes, which could have taken a whole day, if done manually. For one off things like this, it's such a simple tool and really easy to use. 

While there are other ways of doing these type of tasks, e.g., a lot of HR systems have some sort of bulk email feature built-in to send new hires information. Our HRS doesn't have that or maybe it's too clunky to use. This just makes it super quick. 

We also use a lot of similar things with one off SQL automation where we could build a complicated script and run that. However, the bot can run a loop of queries for whatever variable it might be and spit out a report. This takes literally minutes to build and run versus hours if you go different paths. This makes it a very sleek little one off thing.

It is a very stable process. It has been a learning experience for us. We have learned to make some changes in our system to add stability that users were experiencing. They were experiencing the same instability issues that we were having. RPA shed that light. We've made some changes structurally to our IT and business processes to avoid that in the future.

We have seen bugs and had frustrations. When we've done software upgrades, or opened service desk tickets, things can get frustrating because of a slow response. There might be a system outage, where we weren't informed of it until everything at our site went dark. So, we have had growing pains.

Overall, it is quite stable. I have seen some very minor occurrences where Kryon's interactions with Microsoft Office might cause the robot to hang. However, it is about one to two percent of the time where we are seeing this happen. It is such a small percentage that it's not even something that we are overly worried about. This would be where they might have some stability issues, but it could be the Microsoft Office API or how they are interacting together. It is such a rare occurrence that it is quite stable overall.

We are currently in the process of working toward upgrading our Process Discovery install. We are putting it out to a larger user base so we can start pulling in more possible use cases, which may not have been identified by somebody.

We currently have a three to five person developer team. Of that team, three of us would be critical for long-term maintenance.

I would rate the stability an eight out of ten. It is very stable. 

It's reasonable enough. I didn't notice any major issues.

There was one day that Kryon had a problem to do with a certificate change or something like that. The whole Kryon environment was down. Aside from that, it's been quite stable and works smoothly on a daily basis. We haven't faced any problems.

Kryon RPA has decent stability. Once you've built your bot, they run really well. With RPA, you're always a victim of what the client does. The biggest challenge in RPA is managing the customer. A customer might do a version upgrade on something that's out of our control. However, from what we can control, Kryon RPA is a stable solution.

I rate Kryon RPA an eight out of ten for stability.

The only challenge today is that when we migrate to a new version, there is a lot of work. We need to roll it back. Once migrated, we cannot roll it back easily. There are a lot of things that need to change. We've asked Kryon to build a complete package so that migration can easily happen from one version to another version. 

For example, 5.1 to 5.4 was really a nightmare for us. It was more to do with the number of assets we had. When they changed to 5.4, with the new enhancements, some of the scripts were failing after we migrated, and we had a whole list of issues. We had to reconfigure certain elements. It was effort. It was not an easy migration.

Kryon RPA is very stable - we've not had many disruptions, and the product is updated regularly.

The stability has been pretty decent. There are certainly opportunities in terms of stability, but with each subsequent release it gets more and more stable.

I’m not sure yet what I think about the stability of Kryon because we haven't been able to get things constantly running and working. We initially had the server issue. And then, there have been issues with Chrome crashing and the extension.

Right now our usage of Kryon is limited to our shared services team. We're taking care of those processes first. But we have plans to automate as many processes as we can get on our plate and get through.

We did encounter some issues regarding to trigger often but our support team is able to resolved it later. Other than that, it is quite stable.

It's quite stable. Most of the difficulties are coming from the changes on our side.

Kryon RPA is a stable solution, but its stability depends on the version installed in your environment. The most recent version of the solution isn't as stable and has a lot of problems that even the support team isn't able to solve. It's better to use an old version of Kryon RPA that's more stable than the newer versions.

We have tens processes in production. As of now, we haven't had any stability issues. It's working great.

The stability has been great. We've had one incident in a year-and-a-half, where we were down for about four or five hours. It affected everybody, not just our company. As far as I know there was a hotfix that they had to put out. But in all that time there has only been that one day.

It is a very stable product.

We haven't had any instability. It is very stable.

So far, the upgrade process has been smooth, but it does take a few hours. The upgrade process could be better. Right now, it takes a few hours for them to set it up. We must wait to have a shared meeting. They have to wait for us, and we have to wait for their availability. It would be better if we don't have to wait for them, and similarly, they don't have to wait for our availability.

It's pretty stable. I can't think of a major crash.

Right now we're having issues, so you've caught me at a bad time. Once you get it in and working, it's quite stable. Part of the problem goes back to the development. Our biggest frustration at the moment is the time to develop, because we are doing a lot of trial and error. It goes back to that debugging and lack of logs. It takes quite a while at this time, longer than we would like, to move a job or prepare it for production. Once it's done and in production, it's very stable. It's the development part that is the problem. Once in production, it is really stable.

We had some issues, but it's relatively stable. We didn't have any major issues. Their support helped us a lot. Some of the issues we had were because we didn't know how to work properly with the product. But it's working and it's doing its job. I'm relatively satisfied with the system.