<?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/1eb3d078baea42f687248283f9e708b5&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/1eb3d078baea42f687248283f9e708b5-4bab97259e81481f.gif</thumbnail_url><duration>105.429</duration><title>Service Deployment Workflow Analysis</title><description>In this video, I walk through the next version of our deployment process, highlighting the canvas and the railway components. Once the deployment is successful, I expect to see a service deployment triggered, but I noticed an issue with the source of one of the events that initiated a loop situation. It&apos;s crucial to address why this particular trigger occurred. I would appreciate your feedback on this to ensure we can resolve the confusion before moving forward.</description></oembed>