{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/413bce9d4e61451bb2d913325dec7236\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/413bce9d4e61451bb2d913325dec7236-f18b0664d22dbf3d.gif","duration":72.377,"title":"Workflow Bug After Recent Style Change","description":"This Loom focuses on a workflow that has become buggy after a recent style change. The author checks the workflow’s history to find what executed last night, noting it ran 11 steps and shows those steps in the history view. They also describe that last week they ran the steps and saved them, but when they returned, the behavior did not match what was expected. The main issue is that the current workflow execution and saved state appear inconsistent after the change in style."}