I wanted to share an experience we had last week just prior to going live on 2023.2 this weekend. Many of our dashboards were showing old data or it was missing altogether. What we discovered from support was that read-only BAQs connect to your read-only database by default.
Apparently the replication job between the production database and the read-only database had stopped (failed? still have an open ticket). So our dashboards still worked, but the data was 24 hrs old.
This can be changed in the BAQ designer under Actions > Execution Settings > Use Primary Database
What I’m waiting to find out is if this was planned ahead of the upgrade or if the replication stopped working by chance. We’re aware of the work-around now, so if you ever see anything weird, you might need to redeploy your BAQs/Dashboards after pointing the BAQ to the primary db.