ScreenConnect 25.8.3.9459 Breaks Connectwise Automate Integration

Avatar
  • updated
  • Open

I've just been off a half hour chat with Connectwise support after upgrading our ScreenConnect server tonight from 25.7 to the 25.8.3.9459 release. I not only found out that it breaks Automate integration, but more importantly, I found out that internally this is a known issue that is unfortunately not public. 


I am extremely frustrated, given that this is exactly the kind of issue that should either be immediately made public and/or should result in an immediate pullback of the release with an acknowledgement of an issue. This is an issue I could have avoided, with just a little vendor-to-client communication. I'm hoping that by posting this, others will avoid the issue I'm now faced with.


Avatar
0
Doug Terborg
Quote from Carol Brown

Yes, this was a messy release of ScreenConnect. Support knew that 25.8.3.9459 would break the Automate plugin before it went GA. It works again after upgrading Automate's ScreenConnect integration, forcing a refresh of the Solution Center, and then going to 25.8.3.9466. It's still crazy that this wasn't in the release notes. Anything that has to do with Automate should never be a silent break like that.

You and I are in complete agreement on that.

There was no public disclosure that I'm aware of, I needed to get support involved to be aware. Even though the window for issues might have been small, I also expected better disclosure of this. Support was great in assisting me and acknowledged the issue; I see this as a management issue.

Avatar
0
Carol Brown

Yes, this was a messy release of ScreenConnect. Support knew that 25.8.3.9459 would break the Automate plugin before it went GA. It works again after upgrading Automate's ScreenConnect integration, forcing a refresh of the Solution Center, and then going to 25.8.3.9466. It's still crazy that this wasn't in the release notes. Anything that has to do with Automate should never be a silent break like that.

Avatar
0
Doug Terborg

Yes. First, update your ScreenConnect integration in Automate to the latest if you have not already done so. Ensure you force a Solution Center refresh to be sure you got the latest.

Then install the newer ScreenConnect 25.8.3.9466 update. The first one had a broken integration, but it was re-released and the current one resolves the problem.

Avatar
0
justin bailey

Yep - Just ran into this myself. Rolling back is not ideal - have you seen any solution?