@Walter_C 

We are using Liquid Clustering as our first strategy. Our Databricks Runtime is 13.3, and we have a table named status_update containing approximately 30 market IDs, each with a single record. In our pipeline, if any market fails, we need to update the status of the table to 'failed'. We are updating the status in parallel, but we are encountering concurrency issues. Does this mean that Liquid Clustering does not work effectively when we use the UPDATE statement on that table?