<?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/da0c1f0b3b754003b405eb434cdd8e97&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/da0c1f0b3b754003b405eb434cdd8e97-e93b6ef9f626501e.gif</thumbnail_url><duration>289.152</duration><title>Critical Code Improvements for Efficient Token Management</title><description>In this video, I address three critical issues I found in the original code regarding form cleanup. The first issue involves date handling, where jobs failing on a Tuesday and running on a Wednesday were incorrectly categorized as nine days old, causing database clutter. I fixed this by implementing a &apos;created at&apos; check to ensure jobs are processed correctly. The second issue was a performance problem due to looping through expired tokens, which I resolved by converting it to a batch system for efficiency. Lastly, I improved the delete logic by adding filters to prevent risky deletions based on NC strings, ensuring safer database operations.</description></oembed>