Does Railway switch traffic before or after a deployment's health check passes?
Ordering between traffic switching and rollback Railway documents two behaviors that appear to interact: every successful deployment receives a permanent URL alias routing traffic to the current version, and a service rolls back to the previous deployment when a new one fails its health check. What the documentation leaves open is the ordering of those event