I figured it out. I was using the WPSSO FAQ plugin, and while it was still enabled, I had used their custom post type. The CPT was called Questions.
When I disabled it, I had forgotten to make the changes to the accordion list. Disabling it does not remove the data, or the query connections that are already accessing it.
Weeks later, when I made an update to the CPT content for the FAQs, it wasn’t showing in the builder or the front end 'cause it was querying the wrong data. What really puzzles me now, though, is when I created a template, deleted the section, and added it back in from the template, it was querying my FAQ CPT and not the Questions, because I changed the query loop, and it was showing the correct information, so it had to be.
But I’ve noticed that recently in Bricks:
If I make changes to an element and save it, most of the time, it doesn’t save those changes unless I click off of that element first and then save. That way, it updates the data.
The problem that this causes is, all those changes that I make can just disappear. So I select the element, make the changes, hit Save. It’s not on the front end. I click around, make some other changes, save it. Some of those get saved, and many of them don’t. I go back to the previous elements I was editing, and everything’s gone that I did.
Why am I saying this? 'Cause I wonder if that’s somehow connected to why it looked like it had correct data, 'cause I did make the change to the query loop and it didn’t save it.
So, the bottom line is operator error, but there is definitely an issue in Bricks when saving. I’ve hit this problem repeatedly until I figured out that clicking away from an element before clicking save will save the changes; it’s a ritual now. Edit, click a different element, save, and I stopped having that problem.