Unexpected error in REST API: Unable to create database connection. There is no open application

Hi JackLacava 
I truly appreciate your time, and knowledge.

Do you happen to have a link/reference?  I certainly was not aware of this requirement, and in the first round of testing our code was NOT impacted by this change.  (The only impact of the upgrade was the fact that we were unexpectedly required to move our authentication from OIDC to PAT tokens. )

To make matters more interesting, we already deployed the client-side code all the way to *production*, and it seems to be working as-of now (*without* calling "OpenApplication").  It seems like a concern that our production environment is a ticking bomb that is potentially going to stop working any second.

I want to point out that in every REST api call we make, there is a json body that specifies the application name and the base onestream url.  Shouldn't that sufficiently indicate that the application would be auto-opened?  What would be the purpose of "opening" an application as an independent step, if we have no need for the services provided in an SI object.

I should know this by now, but is V8 still a work-in-progress? Are we considered early adopters?  If nothing else, I found that there wasn't any way to get a "breaking changes" document for the V7 -to- V8 upgrade.  I find myself pushing forward by trial-and-error, which is an imperfect experience for software development (... especially when under time constraints, to get things working before the 2025 budgeting season).