Thanks, that is exactly the change I have thought (in changes for 0.5r6).
I will think how to avoid that. It is not a "bug" on my side nor on Cakewalk side, that is unfortunate way both are working at the moment...
The problem is Cakewalk "stopping" surfaces (not calling them) when many dialogs are open. In one of preset we needed that to automate tempo dialog.
So AZ Controller continue working even when Cakewalk engine is paused, but in that state Cakewalk is no longer reporting anything correctly, the project is a kind of "temporary closed". So AZ Controller "think" tracks no longer exist.
Since I don't have motor faders, that has not disturbed me. As you can see I have even forgot that "features" (renovation in progress.... no place for studio devices...
)