@LeonidS and community — closing update + what followed

Just want to close this thread properly as it turned into quite the learning experience and may help others on v14.

Quick recap of what happened:

The fatal 702 error resolved naturally exactly as LeonidS predicted — once the bx_ntfs_ tables were cleanly removed, the cron queue had nothing to process and the spam stopped on its own. Load normalised, notifications loaded instantly, no manual patching needed. Leon was right from the start. 😄

What we didn't expect:

The cron cleanup also wiped our var/sessions/ directory as collateral. This logged every single user out simultaneously. When they all logged back in at once, it exposed a completely separate pre-existing database issue — all Premium membership records in sys_acl_levels_members had an empty State field instead of State = 'active'. UNA silently ignores these records and falls back to Standard level, so every user suddenly showed Standard instead of Premium.

What I fixed:

• Recreated var/sessions with correct permissions → logins restored
• Fixed State = '' on all 1037 Premium membership records → State = 'active'
• Cleaned up expired Premium rows that were overriding valid ones
• Fixed profile ID mismatches where sys_accounts.profile_id pointed to a profile with no ACL row

Tip for other v14 admins:

If users suddenly show the wrong membership level after any module uninstall or cron cleanup, check sys_acl_levels_members. State first — an empty string silently breaks ACL lookups without throwing any errors. Easy to miss, painful when it hits at scale.

Thanks again @LeonidS for the fast and accurate diagnosis on the notifications side. Brilliant support as always. 🙏