# Klipper 'mcu' shutdown: timer too close **URL:** \ **Category:** General Discussion\ **Created:** [October 15, 2023, 4:51pm UTC](https://klipper.discourse.group/t/klipper-mcu-shutdown-timer-too-close/10995 "2023-10-15T16:51:48Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![LifeOfBrian](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/lifeofbrian/32/2380_2.png) [@LifeOfBrian](https://klipper.discourse.group/u/LifeOfBrian)\ **Post date:** [October 16, 2023, 6:33am UTC](https://klipper.discourse.group/t/klipper-mcu-shutdown-timer-too-close/10995/5 "2023-10-16T06:33:22Z")
Check this for better understanding: > [@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/klipper-mcu-shutdown-timer-too-close/10995)._