<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/aae39ca8b31f4c01bf42e1b5c47d32be&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/aae39ca8b31f4c01bf42e1b5c47d32be-b6d56dee6adc88b5.gif</thumbnail_url><duration>129.131</duration><title>Resolving Stale Data Issues in Your Table 📊</title><description>In this video, I walk you through the issue with the last cell not running in our table, which stemmed from a stale data error in the manufacturing identifier. This occurred because the manufacturing final result field wasn&apos;t evaluating correctly, and changes were made to the column configuration while the table was off. As a result, the last row didn&apos;t receive the most up-to-date manufacturing value and was left out of the updates affecting the other 16 rows. To resolve this stale data issue, I recommend re-running the cells displayed in grey, or you can filter for the specific column to re-run all affected rows. Please take action on this to ensure everything is up to date.</description></oembed>