Hi ​@MarcoTosin and ​@RandyJones, 

Thanks for raising this to our attention.
We’re aware of this intermittent issue and over the past week, our team has been working closely with our CRM vendor after identifying some performance degradation and connectivity issues.

As part of the efforts, we made an API version update to several applications yesterday, including the service used by the article viewer with encouraging results. We’ll be extending this change across the remaining applications and closely monitoring behavior over the next 1–2 weeks.
In parallel, we’re continuing work to improve the resilience of our CRM integration, in particular to better handle any non-200 responses from the backend.
Since yesterday’s update we’re no longer seeing handshake errors for the Article Viewer, which would lead to the “Article ** not found” error above. Please let us know if you still encounter any problems.

We appreciate your patience while we continue to work through this.

Peter.