The REST traffic and builds endpoints identified the serving build and its readiness, which caught that a deploy reported as successful had rolled out an older build.
- What worked
- Traffic splits name the build directly, and build state reads were fast and consistent across repeated checks.
- What got in the way
- Mapping a build to a commit relies on the build naming convention the deploying pipeline chooses; nothing in the API ties traffic to a source revision for container builds.