# Dgraph missing mutations in Ludicrous mode (post mortem)

**URL:** <https://discuss.dgraph.io/t/dgraph-missing-mutations-in-ludicrous-mode-post-mortem/11019>\
**Category:** Dgraph\
**Tags:** discussion, postmortem, dgraph\
**Created:** [October 19, 2020, 9:08am UTC](https://discuss.dgraph.io/t/dgraph-missing-mutations-in-ludicrous-mode-post-mortem/11019 "2020-10-19T09:08:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rahul](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/rahul/32/3645_2.png) [@Rahul](https://discuss.dgraph.io/u/Rahul)\
**Post date:** [October 19, 2020, 9:08am UTC](https://discuss.dgraph.io/t/dgraph-missing-mutations-in-ludicrous-mode-post-mortem/11019/1 "2020-10-19T09:08:12Z")

</div>

**Problem**

When running Dgraph in ludicrous mode, Dgraph overrides sequential upserts on any attribute.

For example, for the following schema:

```auto
name: string @index(exact) . 
email: string @index(exact) .
friends: [string] . 

```

If we send 3 mutations that add a friend to a friends list, only one friend i.e. the one added in the last mutation gets added.

**Why this is happening?**

We didn’t used to update startTs for upsert mutations post [this change](https://github.com/dgraph-io/dgraph/pull/5701) So, we end up assigning the same startTs across different mutations because we don’t increment the max assigned timestamp. This startTs is eventually passed as commitTs to CommitToDisk method in mvcc.go. So same commitTs across 2 different mutations leads to the latter mutation overriding former mutation. Hence the bug.

[Fix is just a one line change](https://github.com/dgraph-io/dgraph/pull/6754/files)