<?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/28e56e97da944cc18144b9c92594b8e5&quot; frameborder=&quot;0&quot; width=&quot;1836&quot; height=&quot;1377&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1377</height><width>1836</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1377</thumbnail_height><thumbnail_width>1836</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/28e56e97da944cc18144b9c92594b8e5-712c84d5907caeb6.gif</thumbnail_url><duration>181.1391</duration><title>Stress Testing and Message Editing Techniques 🔧</title><description>In this video, I conducted some extra stress testing by printing messages at various points during the shuffle process. I demonstrated how editing messages affects the checkpoint restoration, particularly when only the message is changed. I also highlighted an edge case where restoring a checkpoint undoes all changes, including any new messages added. I encourage you to pay attention to how these changes impact our workflow and consider how we can optimize our processes moving forward. Please let me know if you have any questions or suggestions based on what I&apos;ve shared.</description></oembed>