Can we safely disable the

notify_ui_{steps, tasks}_v3

triggers on the database tables for some time? To resolve this outage in our systems I have decided to delete/archive some more rows from our tables, but the presence of these triggers makes the process extremely slow to the point of choking the entire database. Wondering if disabling these triggers temporarily would cause any permanent damage to metadata service?

Yep - this will just make the UI not live update but no issue with executing any metaflow runs by themselves