Stopping a debug session is damaging the sql table current in use

Stopping a debug session is damaging the sql table current in use

  
When I stop a debug session using outsystem stop button, the current table in use only can be recovered with an sql server reboot or a truncate and restore data. Anyone can say something about?
Regards.
Hi Rogerio,
If you run that same action without the debug session on, does that problem with sql server still occur? If so, it's a problem that occurs from your action and not the debug session.
If it's a debug session problem, you can try to use "abort request" button on debugger instead of "stop debug".

If it's only a debug session problem, it might be a good idea to report this to OutSystems.
Hi, we are rebuilding an existing system now using OuSystems, then it is an old Stored Procedure, very often tested. It looks it is a debug problem and several minutes (even hours) after the unavalable table becomes available again with no data loss. The problem occurs after a call to an external SP when I abort or stop after found some error working with the returned results.
If it happens again, I will report.
Thanks