# "Timer Too Close" at a consistent time in file **URL:** \ **Category:** General Discussion\ **Created:** [March 20, 2024, 2:48pm UTC](https://klipper.discourse.group/t/timer-too-close-at-a-consistent-time-in-file/15093 "2024-03-20T14:48:41Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [March 20, 2024, 3:56pm UTC](https://klipper.discourse.group/t/timer-too-close-at-a-consistent-time-in-file/15093/2 "2024-03-20T15:56:00Z")
Maybe you can try lowering the extruder microsteps at least for testing purpose. Otherwise I think you already read through 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/timer-too-close-at-a-consistent-time-in-file/15093)._