The solution's stability is good. As long as it's deployed the right way, it's relatively stable.

The on-premise software has some bugs. We get signed out every time.

It's quite stable.

Bizagi is a very stable solution.

The stability is pretty good. We don't have problems with Bizagi.

At the moment we are having a bit of a performance issue, but we are monitoring it to find out what is happening. It's taking a bit longer than we would like. That would be something that we would activate support for, but we don't have access to support right now.

Even though our company paid for support, it wasn't activated because of problems with the partner. We paid for the support license, but the partner didn't pay Bizagi. So we don't have support. But we should have it back in a week or so.

The performance issue is quite annoying. It's not fatal, just slow to approve and it takes five minutes to open the user options screen. It wasn't like this before.

Even a cloud solution is heavier. Whereas, my experience with Bizagi is that it is faster. For example, in Colombia, the country where I teach, the average bandwidth of the internet is not as it is in the US, Canada, or other countries where I was working with these kinds of tools. When you use the cloud, you need to optimize resources. With Bizagi, I haven't experienced lags, so I didn't think that I was losing time waiting for processes. Sometimes, within other tools, I need to wait or have to wait longer for exportation, like a simple PDF files exportation or maybe Exchange files to connect with other programs or other software. However, with Bizagi, the processes are lighter and faster.

The functionality we are using is somewhat stable, but when they have new functionalities, new widgets, or even a new version, they have a lot of bugs and it seems that the users are their QA team. We have to report a lot of things, but that's mostly in new versions. When we have a stable version, we don't have a lot of bugs, but when we want to try new things, there are a lot of bugs.

I would rate the stability of Bizagi as a seven out of ten.

The solution's stability is excellent. It does freeze very rarely, but it's quick to go back to normal when that happens.

It is stable. We have a good impression of its stability and don't have any issues.

I haven't had any problems, this is a stable solution. 

The stability of the product is fine, I have not had any issues in regards to this manner.

I rate the tool’s stability a seven out of ten.

Stability has been improving of late with the aggressive investments Bizagi is making in support and QA.

It is quite a stable solution. I rate its stability as an eight.

The solution is very stable. 

The solution is quite stable. There aren't any problems with bugs or glitches and it doesn't crash or freeze. It works well.

The solution is very stable. We haven't found any bugs or glitches. The solution doesn't crash. It's quite reliable.

Bizagi was stable. The performance was okay on my normal computer, but I felt that I wanted to move to other options. 

We have had some problems with bugs. If you are converting and exporting into SharePoint and you have long path names, there's a limitation in part on the length of path names on SharePoint. We had problems with that. We got the new version just a couple of weeks ago and that solved the problem. Right now we don't have any issues with stability. 

The reply from Bizagi was understanding. They did not really see the problem right away, however, we figured out it was a mix between the versions of SharePoint and the version of Bizagi that we had. 

The machines are stable. They stay stable 90 to 99% of the time.

Bizagi is a stable solution.

I have not experienced any bugs or errors, so I think that it is stable.

It is very stable and we have not had any problems.

It is stable.

I would rate the product's stability a nine out of ten.

So far its stability is good. It's not presenting a challenge. At the moment we are doing little experiments and so far it's not a problem.

It is stable. We didn't have any crashes or other similar things.

Its stability is very good.

The tool is fairly stable. However, being based on Windows, it has its own set of challenges.

Sometimes it requests me to update Bizagi and it takes some time working on it. It can be a challenge to update it when I don't have internet access.

I'm not sure I can comment on stability just yet, but I did have an okay experience. I didn't have any issues.

With Bizagi, initial loading is extremely slow.

After upgrading our original Bizagi 10.6 install to Bizagi 10.7, the case re-assigning feature stopped working. Bizagi provided different hotfixes, which caused other problems. It was finally fixed on the fourth try.

There are no problems with the general stability of the product. Sometimes when you close a file and try to reopen, it says it didn't connect. Other than that the stability is perfect. 

After your process is working, it's good. There are no problems. but sometimes support fixes affects other functionalities.

Once the issues with integration were solved, our clients have not found any problems with respect to stability.

No. In production the application proved to be very robust, fast and reliable.

Bizagi is very, very stable.

This is a very stable solution, and we have had no bugs in the past four years.

Besides for the performance issue, it is stable. 

Yes, sometimes when we execute EXPRESSIONS Xpath, we don't always get the same result.

Only when opening multiple processes or the process itself is big and multiple objects is selected.

This is also noticed mainly when you try to organize the process model and use stages.

In terms of the stability, sometimes it runs too slowly. 

No.