ScotRail services are experiencing revisions and some replacements with buses due to a fault in the signalling system between Edinburgh Waverley and Haymarket. This issue was detected around 2 pm on Sunday. Network Rail confirmed that some services will be delayed by up to 30 minutes, and some trains will be cancelled as a result of the fault. Network Rail engineers are working to fix the fault, and disruption is expected at the station and surrounding lines until approximately 3:30 pm. A replacement bus service has been established at Haymarket, Edinburgh Park, Linlithgow, and Bathgate. ScotRail directs passengers to use their app for journey information during this time.

The narrative structure relies on establishing a cause (signalling fault) followed by an inevitable consequence (delays, cancellations, bus replacements). The key dynamic here lies in the tension between official assurances of repair and the immediate, tangible disruption experienced by passengers. The use of explicit timelines (2 pm detection, 3:30 pm expected end of full disruption) attempts to create a sense of bounded uncertainty, which, while factual, can also manifest as manufactured expectation management. The pattern suggests a reliance on established infrastructure—Rail/Network Rail protocols—as the primary frame for managing an acute failure. A critical question is what happens when the stated timeline (3:30 pm) is breached, or if the fault's scope is underestimated by the initial assessment. Furthermore, the shift in service provision from rail to bus highlights a systemic vulnerability where operational failures immediately necessitate a less efficient, alternative solution, underscoring the fragility of integrated transport systems when core signalling fails. What underlying assumptions about redundancy and recovery planning exist within this system that are being tested by this localized failure?