# Beeminder doesn't think long term enough (ridiculous x-max causes error)

**URL:** <https://forum.beeminder.com/t/beeminder-doesnt-think-long-term-enough-ridiculous-x-max-causes-error/4496>\
**Category:** Bugabee\
**Created:** [November 1, 2018, 10:40pm UTC](https://forum.beeminder.com/t/beeminder-doesnt-think-long-term-enough-ridiculous-x-max-causes-error/4496 "2018-11-01T22:40:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![eugeniobruno](https://avatars.discourse-cdn.com/v4/letter/e/f475e1/32.png) [@eugeniobruno](https://forum.beeminder.com/u/eugeniobruno)\
**Post date:** [November 1, 2018, 10:40pm UTC](https://forum.beeminder.com/t/beeminder-doesnt-think-long-term-enough-ridiculous-x-max-causes-error/4496/1 "2018-11-01T22:40:32Z")

</div>

I wanted to take a look at what my graph would look like in 2039. Looks like beeminder isn’t seeing the big picture.

December 2037 works, so I assume something somewhere uses 32 bit?

It says it pings the team. Sorry about that 🙂 Clearly not an important problem… yet. I sure hope you’re around in 60 years because my life is going to become a mess the second beeminder goes down. 😛

 ![image](https://us1.discourse-cdn.com/flex019/uploads/beeminder/original/2X/f/f81119ba2535548aba29cdaec2b7a147e0f24640.png)

---

<div class="post-metadata">

**Author:** ![howtodowtle](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/howtodowtle/32/2284_2.png) [@howtodowtle](https://forum.beeminder.com/u/howtodowtle)\
**Post date:** [November 12, 2018, 5:44pm UTC](https://forum.beeminder.com/t/beeminder-doesnt-think-long-term-enough-ridiculous-x-max-causes-error/4496/2 "2018-11-12T17:44:42Z")

</div>

Yep, I think 2038-01-17 is the max and I believe it’s intended. At least that’s what any later date reverts to in the road builder. 🙂
