In Progress

Modeller responsivness really slow and lagging when selecting, moving items

I have been having this issue for some time now (even on the latest 64bit version). As I am documenting a process I would sometime need to re-organise the direction of the process flows, which often involves multiple selecting items and moving and aligning.

What has been plaguing this app for me is that sometimes the process is incredibly slow. Anyone can easily replicate this issue:

- Start with a blank model,

- Create 10 linked tasks in different places,

- Select them all,

- Press align horizontally,

- Press align vertically

Expect this last action to take around 40 seconds to complete. It also doesn't matter if it's vertically first then horizontally after, this is just an example to get the modeler to change a number of items at once - that amplifies the fact that it's quite slow per item in general.

If (let's assume) you performed the above steps and the align vertically was pressed by mistake, the undo function takes just as long.. I do not think that a time interval of nearly a minute and a half (+40 sec and + 40sec) in case of a mistaken button press is acceptable.

As for specs, I think these are more than enough:

OS Name Microsoft Windows 10 Enterprise

Version 10.0.16299 Build 16299

System Model HP EliteBook 840 G3

System Type x64-based PC

Processor Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400 Mhz, 2 Core(s), 4 Logical Processor(s)

Installed Physical Memory (RAM) 8.00 GB

Any suggestion on how to solve this issue would be helpful.

Comments (6)


Dear Kevin,

We were able to reproduce it. We have escalated it to our produce team.

As soon we receive news, we will write back.



much appeciated - Thanks


I need to know something about this soon please. Our company works with Bizagi and I need to work in a process right now, but the speed to move flows and other elements does not allow me to do almost anything. This happens since the last update I installed. I do not understand why but I have not found a solution on the web or on their own site that allows me to solve this. Please indicate if it is an issue that is still under investigation or in a phase close to delivering a certain type of solution for users. I understand that the software is free but I also believe that it does not imply that this type of error occurs. I have been working with bizagi since I was in college and before that I thought I was a great process modeler. After modeling issues were added, it seems to me that the BPMN approach that was previously available was lost and delivered a simple but powerful tool to document all kinds of processes.

I leave my personal mail please to keep me up to date if they manage to find an answer or solution or simply to return to the last previous version of the program that did not have this type of error.

I am very attentive to your comments.

I await your answers

Miguel Lefever


Dear Miguel,

Our product team is still analysing this performance problem. Please explain us the steps to use to reproduce your issue.

We look forward to hearing from you


Dear Kevin and Miguel,

We have improved the performance of the modeler. Please proceed to download our latest installer which includes some FIXES including this one. Version

Best Regards


Hello Juan,

Thank you for your assistance and information regarding the fix. I have installed the version you mentioned and can confirm that in fact align and distribute buttons work well.

The issue with slow responsiveness is still present though through other actions.. In my original e-mail I mentioned the align action to illustrate the issue, however the scope of the issue is wider than just the align actions. In the latest version for instance I noticed that in the same scenario as in the OP (i.e. create 10 processes) the first item movement following an align or distribute results in the same unresponsive UI as before. i.e.

- on a blank model, create 10 processes,

- select them all, align or distribute on any axis,

- with the items all selected, drag them in any distance in any direction.

Result is the same 40-50 second wait of unresponsive UI.

I hope this helps to stamp out any usability issues that other users seem to also be having. Let me know if there's anything I can help with.