The stability of the solution is quite good. It doesn't crash or freeze. It's not buggy and doesn't seem to have glitches. We find the performance to be reliable so far.

I give the stability an eight out of ten.

The software's stability is great, but you have to be very careful about the environment you have it running in because you have to make sure you have this much memory and backend processing because Automate can be resource-intensive. Of course, that depends on how many tasks you run on the application, and the more tasks you run, the more resources it uses.

Its stability can be better. It's not a very big concern, but once in a while, you lose connection to the main central server for Automate from the developer console. If your developer console loses connection to the main console, which is not a very frequent occurrence, you don't realize it until later. So, you're saving your task thinking it's working fine, but it's not being saved on the server. You lose a little bit of data once in a while, but these are not very frequent occurrences. It happens once in a while, but it's something to be careful about. There are also occasional crashes. Sometimes it slows down, and it crashes. I'd rate it an eight out of ten in terms of stability.

The stability depends on the task; there are some performance issues when working with massive files, but the solution is otherwise stable. It processes files in milliseconds, while database retrieval and file manipulation are rapid. It slows down when we run a process record by record doing multiple calculations. It's good that once we build a task, it's repeatable.

Never had stability issues with Automate. Any downtime we've had was caused by other systems, not Automate itself. That's why a free development environment is crucial. We need to test and build without impacting production.

So, the only major improvement suggestion is a free development environment. That would solve our downtime issues and allow us to develop and test automation efficiently without affecting production.

The solution is stable.

The stability of the solution is excellent. There are no bugs or glitches. It doesn't crash or freeze. It's very reliable.

For the most part, the solution is stable. We're still finding ways to program around hiccups in our runs.

It's fairly stable. We're seeing some issues. I'd rate it a seven out of ten in terms of stability.

The solution is stable. It's reliable. There are no bugs or glitches. It doesn't crash or freeze.

It's a distinct challenge. We lack a direct path to the internet; instead, our server connections pass through Argentina, and our Microsoft server is situated in Brazil or the United States. This setup sometimes causes connectivity issues, leading to timeouts. We're actively addressing these concerns within our cloud environment, but overall stability relies heavily on our internet infrastructure, which currently impacts the functioning of our entire setup.

The stability is very good. As far as I know, we haven't had any issues so far. It's very reliable. The performance is good.

This is a very stable product.

We aren't completely satisfied with the stability The system can slow down and the program occasionally crashes and closes. 

Sometimes my team reports situations where there are some unexpected errors from the tool. For example, if a Java error is reported then it doesn't mean anything at all to the end-user. This is an area that may also have room for improvement, although, at perhaps two or three times in a project, this does not happen often.

In some older versions there were some instabilities, but the latest version (v.11) seems very stable.

The solution was quite stable. We didn't have to deal with bugs or glitches. It didn't crash or freeze. We found it to be reliable for the most part.