# Datoms API in dev-local does not show recently transacted data

**URL:** <https://forum.datomic.com/t/datoms-api-in-dev-local-does-not-show-recently-transacted-data/1672>\
**Category:** Datomic Cloud\
**Created:** [October 23, 2020, 8:25pm UTC](https://forum.datomic.com/t/datoms-api-in-dev-local-does-not-show-recently-transacted-data/1672 "2020-10-23T20:25:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tony.kay](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/tony.kay/32/316_2.png) [@tony.kay](https://forum.datomic.com/u/tony.kay)\
**Post date:** [October 23, 2020, 8:25pm UTC](https://forum.datomic.com/t/datoms-api-in-dev-local-does-not-show-recently-transacted-data/1672/1 "2020-10-23T20:25:44Z")

</div>

I’m trying to write a test of a function that uses the datoms function. I transact data, and get back a db-after that contains the new data; however, if I run `datoms` on `db-after` or even a call to `(d/db connection)` I do not see the datoms in the stream.

This test was working fine with an on-prem memdb, but I’m trying to port it to the memdb support of dev-local. I see all of the base schema datoms.

I’m guessing the “live index” in dev-local isn’t included in the db-after?

---

<div class="post-metadata">

**Author:** ![tony.kay](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/tony.kay/32/316_2.png) [@tony.kay](https://forum.datomic.com/u/tony.kay)\
**Post date:** [November 5, 2020, 5:51pm UTC](https://forum.datomic.com/t/datoms-api-in-dev-local-does-not-show-recently-transacted-data/1672/4 "2020-11-05T17:51:16Z")

</div>

The problem was that I was used to the on-prem API, and the cloud API honors the `:limit` parameter, which I was not supplying. The doc-string did mention it, but I missed it.