# Interpretation Help needed: MCU 'mcu' shutdown: Timer too close **URL:** \ **Category:** General Discussion\ **Created:** [April 25, 2024, 12:26pm UTC](https://klipper.discourse.group/t/interpretation-help-needed-mcu-mcu-shutdown-timer-too-close/16022 "2024-04-25T12:26:19Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [April 25, 2024, 12:37pm UTC](https://klipper.discourse.group/t/interpretation-help-needed-mcu-mcu-shutdown-timer-too-close/16022/2 "2024-04-25T12:37:51Z")
Hello @HowlingCoder ! You may have a look here: > [@Timer too close](https://klipper.discourse.group/t/timer-too-close/6634): > > Timer too close Background A “Timer too close” error occurs when the MCU is asked to schedule an action at a time that is already in the past. This typically results from delayed communication between the host and the MCU - for instance, if the host was busy or the message was blocked en route. warning Important: Klipper can identify what command was too late, but cannot determine why the delay occurred. The root cause is often external - such as USB congestion from a webcam or high system … --- _[View the full topic](https://klipper.discourse.group/t/interpretation-help-needed-mcu-mcu-shutdown-timer-too-close/16022)._