# \`global LatestTimestamp\` is 0 in when debugging from dryrun txn

**URL:** <https://forum.algorand.co/t/global-latesttimestamp-is-0-in-when-debugging-from-dryrun-txn/6117>\
**Category:** General\
**Tags:** teal\
**Created:** [February 25, 2022, 2:39am UTC](https://forum.algorand.co/t/global-latesttimestamp-is-0-in-when-debugging-from-dryrun-txn/6117 "2022-02-25T02:39:05Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![fabrice](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@fabrice](https://forum.algorand.co/u/fabrice)\
**Post date:** [February 22, 2023, 8:09pm UTC](https://forum.algorand.co/t/global-latesttimestamp-is-0-in-when-debugging-from-dryrun-txn/6117/10 "2023-02-22T20:09:04Z")

</div>

Welcome to Algorand !

After discussing with the team, it looks like the best options right now are:

- use `dryRun` if you can
- otherwise, replace the timestamp check logic by some logic that does not have that issue for testing, or design it to work with with sandbox

---

_[View the full topic](https://forum.algorand.co/t/global-latesttimestamp-is-0-in-when-debugging-from-dryrun-txn/6117)._