# Incomplete History because exceed length

**URL:** <https://community.temporal.io/t/incomplete-history-because-exceed-length/13532>\
**Category:** Community Support\
**Tags:** go-sdk, general-impl\
**Created:** [September 13, 2024, 8:16am UTC](https://community.temporal.io/t/incomplete-history-because-exceed-length/13532 "2024-09-13T08:16:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anang\_Pambudi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/anang_pambudi/32/5794_2.png) [@Anang\_Pambudi](https://community.temporal.io/u/Anang_Pambudi)\
**Post date:** [September 13, 2024, 8:16am UTC](https://community.temporal.io/t/incomplete-history-because-exceed-length/13532/1 "2024-09-13T08:16:55Z")

</div>

I got this error on my temporal log.

> Incomplete history: expected events [1-342] but got events [1-335] of length 335: isFirstPage=true,isLastPage=true,pageSize=256

I was looking for some references and it said that possibility because it is forced to show event list in one page (isFirstPage = true & isLastPage = true).  
I wonder if this error was issue or just log? and how to solved it?

---

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [September 13, 2024, 2:52pm UTC](https://community.temporal.io/t/incomplete-history-because-exceed-length/13532/2 "2024-09-13T14:52:42Z")

</div>

This sounds like DB issue. Is your DB replicated?

---

<div class="post-metadata">

**Author:** ![Anang\_Pambudi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/anang_pambudi/32/5794_2.png) [@Anang\_Pambudi](https://community.temporal.io/u/Anang_Pambudi)\
**Post date:** [September 23, 2024, 3:39am UTC](https://community.temporal.io/t/incomplete-history-because-exceed-length/13532/3 "2024-09-23T03:39:36Z")

</div>

Yes. is it causing the issue?

---

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [September 23, 2024, 5:05am UTC](https://community.temporal.io/t/incomplete-history-because-exceed-length/13532/4 "2024-09-23T05:05:49Z")

</div>

Temporal expects strong read-after-write consistency from the DB. Most DBs don’t provide such consistency during failover and are incompatible with Temporal.

---

<div class="post-metadata">

**Author:** ![Anang\_Pambudi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/anang_pambudi/32/5794_2.png) [@Anang\_Pambudi](https://community.temporal.io/u/Anang_Pambudi)\
**Post date:** [September 23, 2024, 6:09am UTC](https://community.temporal.io/t/incomplete-history-because-exceed-length/13532/5 "2024-09-23T06:09:08Z")

</div>

is there any approach I could take to handle this issue? I think it’s not possible to remove DB replication from the architecture

---

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [September 24, 2024, 3:05pm UTC](https://community.temporal.io/t/incomplete-history-because-exceed-length/13532/6 "2024-09-24T15:05:05Z")

</div>

Switch to DB, which provides read-after-write consistency in case of failover.