This in not just a 2025 event, it was common with last year's program. Not with every return, but many. That may be why it's not solved this year either. They haven't pinpointed (looked) for a specific non-global trigger.
If an answer solves your issue, click on the "Accept as Solution" button! Makes it easier for people to find answers to similar questions that have already been posted.
