video1.0<iframe src="https://www.loom.com/embed/23fc23ff33234cabadb3d344db9da0c0" frameborder="0" width="1152" height="864" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>8641152Loomhttps://www.loom.com8641152https://cdn.loom.com/sessions/thumbnails/23fc23ff33234cabadb3d344db9da0c0-b47c5057e668945d.gif71.441This Loom explains how an automated deployment decision is paused when a saved traffic assumption becomes invalid. The deployment was approved because traffic matched an assumption of 1000 requests per minute, and that assumption was stored in MongoDB. After the deployment started and was running, traffic jumped to 3500 requests per minute. When MongoDB and Firebox detected the related assumption was no longer true, the deployment was paused.