{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/8d65327fcb0649d6b06c0ca028eaf934\" 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/8d65327fcb0649d6b06c0ca028eaf934-9a9c1bec473e0219.gif","duration":136.587,"title":"Catching AI Feature Issues with Guarded Rollouts 🚀","description":"In this video, I share how LaunchDarkly's Guarded Rollouts helped me catch a regression in an AI feature before it became a major issue. I was rolling out a new model, GPT-40, and used the Guarded Rollout feature to monitor key metrics like completion error counts and feedback. Thanks to this feature, LaunchDarkly automatically rolled back the change at 9:53 p.m. while I was asleep, preventing a potential incident. I encourage you to try out this feature and let me know your thoughts. Stay tuned for updates as I continue testing!"}