# PQS Ledger offsets seem to be off

**URL:** <https://forum.canton.network/t/pqs-ledger-offsets-seem-to-be-off/7238>\
**Category:** App Development\
**Tags:** pqs\
**Created:** [May 16, 2024, 12:27am UTC](https://forum.canton.network/t/pqs-ledger-offsets-seem-to-be-off/7238 "2024-05-16T00:27:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![huw](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/huw/32/2343_2.png) [@huw](https://forum.canton.network/u/huw)\
**Post date:** [May 16, 2024, 12:27am UTC](https://forum.canton.network/t/pqs-ledger-offsets-seem-to-be-off/7238/1 "2024-05-16T00:27:16Z")

</div>

Hi there, I am encountering some strange behaviour with PQS. I use `submitAndWaitForTransactionTree` to create a contract and get the ledger offset from the response. I then find the contract that I just created using the `active()` function provided by PQS. The offset available in the result of `active()` appears to be greater than the offset returned by the ledger API. I am testing this on Daml sandbox.

---

<div class="post-metadata">

**Author:** ![huw](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/huw/32/2343_2.png) [@huw](https://forum.canton.network/u/huw)\
**Post date:** [May 16, 2024, 12:47am UTC](https://forum.canton.network/t/pqs-ledger-offsets-seem-to-be-off/7238/2 "2024-05-16T00:47:40Z")

</div>

After doing some more investigation, it seems that this issue only occurs if I run the query immediately after scribe has started (and the health check returns OK). If I add a delay of a few seconds and then run the command and the query, it works as expected