Another new release that doesn't fix this known problem, and the post about it before (https://community.quicken.com/discussion/comment/20542096) has been closed to comments. When can we expect a fix for this highly disruptive problem?
Hello @SabrinaBask,
Thank you for reaching out.
This issue is still being actively worked on by our development team under ticket CTP-15440. At this time, the fix is planned for a future update release, but we do not have an estimated timeframe to share at this time.
Regarding the previous discussion, it was closed due to 30 days of inactivity. hreads in the Community are routinely closed after 30 days without activity, regardless of whether the reported issue has been resolved.
We appreciate your patience while our teams continue working toward a resolution.
Thank you!
