# Rescheduled timer in the past

**URL:** <https://klipper.discourse.group/t/rescheduled-timer-in-the-past/6635>\
**Category:** Knowledge Base\
**Created:** [February 13, 2023, 11:17am UTC](https://klipper.discourse.group/t/rescheduled-timer-in-the-past/6635 "2023-02-13T11:17:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [February 13, 2023, 11:17am UTC](https://klipper.discourse.group/t/rescheduled-timer-in-the-past/6635/1 "2023-02-13T11:17:55Z")

</div>

### Background

Whereas _Time too close_ rather indicates an overloaded / jammed host, this error points to an overloaded MCU

### Reasons

- Too high step rate

### Potential solutions

- Check for approaching the limit:
  - Check the [Benchmarks](https://www.klipper3d.org/Benchmarks.html) document and find the _3 stepper_ value for your MCU type
  - Check the `klippy.log` file and find lines similar to `queue_step 0: t=72950209107 p=7317 i=28714 c=-29 a=214`
  - If the `i=xxx` values are about the same or even lower than the _3 stepper_ value from the MCU benchmark then too many steps are requested

- Reduce the `microsteps` setting of the steppers (typically X and Y)
- Reduce printing speed
- Also see [Advanced Trouble-Shooting / Graphing Klipper](https://klipper.discourse.group/t/advanced-trouble-shooting-graphing-klipper/6613#graphing-the-mcu-7)