You need to construct the logs inside your robot. You can't see this already constructed. So this is a kind of difficulty inside the tool. But in general, I think it's very stable.

As of now, it's stable. I'm using version 23, which is pretty stable. They have some issues with the terminal where there are some restrictions related to screen sizes, but they seem to be working on that.

It's a very stable and clear platform. Also, there's a local representation of IBM, which is valuable for us as integrators and our customers in Greece.

It is very stable and always offers updates.

I rate the solution's stability as five out of ten because the server site experiences memory overload. Similarly, the client's site encounters high memory usage when specific applications remain open for two to three days.

I would rate the stability of this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

So far, no complaints. 

The tool’s stability is good. I rate the stability an eight out of ten.

I think that it is a stable solution but I am not yet experienced enough to answer with certainty.

For now, it is stable because the best thing we have is the scalability as part of our cloud-native application. 

I rate the solution’s stability an eight out of ten.

While we found version 10 to not be quite stable enough, version 11 is much better in this regard. It's still not 100% stable, however, I would estimate it's now at 90-95% stable, which is quite good.

We have not really explored it as much as we would like yet. That is something we are going to start focusing on. We wanted to try it out as a PoC to see how it worked. So far, it has been good. 

This solution is still evolving. It is going through the rounds right now. We hope it will become more stable, but right now, since it works on the laptop, it has a lot of dependency on your browser or what type of operating system you have. Sometimes it has dependency on your credentials - are you using a network type of an ID or a local ID, etc. The use case has to be selected properly and then, accordingly, once you scale it up, it works fine. But the use-case selection becomes key here.

I rate the solution’s stability a six out of ten.

It's stable.

Several products are incorporated in the back for automation. Some of them are in the process of being more aligned with cloud services. Some are still not in Kubernetes or a Docker. Two of them are in the process of being incorporated into Kubernetes and Docker to be aligned with the rest of the products. All of them work in a very stable way.

The solution is quite stable. 

It's pretty stable.

IBM Robotic Process Automation should be more stable.

IBM RPA is an unstable solution. This is the biggest issue we have right now.